Repository navigation
Release 0.1.0a16 - #56
Merged
Merged
Conversation
added 8 commits
October 19, 2026 21:17
Bump the Python package and browser Studio bundle to 0.1.0a16, the desktop product to 0.1.0-alpha.16 with native installer counter 0.1.16, and the Agentic and Files workers to 0.1.8 pinned to core 0.1.0a16. Regenerate the core, worker and Cargo lockfiles and point the documented install commands at v0.1.0a16.
Turn the unreleased notes into the 0.1.0a16 section, grouped by area, and add what had not been listed yet: Studio's Operate area, the new editor's canvas, and the test and CI changes. Drop the call compiler's note that child runs do not start yet, now that they do. Add the alpha16 upgrade row and turn the notes after alpha15 into what changes in alpha16, with the measured migration times, upgrading CLIs and SDKs with the server, and finishing runs that use calls or loops before any rollback.
Add the Studio and security journeys that run against the real platform, the Acme test service fixes and the corrected private-origin wording to the 0.1.0a16 changelog, and tell contributors in the alpha16 upgrade notes that the Acceptance workflow now runs them on every pull request.
State which local, PostgreSQL and acceptance checks passed before tagging, and which checks did not run or are not verified for this release.
Move the workflow graph, Studio capacity resend and platform user fixes into the Studio, desktop app, and CLI notes, and the check failure summary into development and testing.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepares Firefly Weave 0.1.0a16 for release. The owner approved publishing 0.1.0a16 once L7 (#54) and X1 (#53) merged; both have.
Versions
pyproject.toml,firefly_weave.__version__,uv.lock)0.1.0a16firefly-weave-studio-0.1.0a16.zippyproject.toml,uv.lock)0.1.8, pinning core==0.1.0a16tauri.conf.json,Cargo.toml,Cargo.lock,package.json,package-lock.json)0.1.0-alpha.16wix.version, macOSbundleVersion)0.1.16v0.1.0a16Lockfiles were regenerated with their tools (
uv lockfor core and both workers,cargo update --workspace --offline,npm install --package-lock-only --offline); each changed only the bumped version lines. Schema head becomes0033_language_workflow_calls(three new migrations:0031_operations_key_collation,0032_operations_facts,0033_language_workflow_calls); no role is added or changed.Changelog and upgrade notes
## Unreleasedbecomes## 0.1.0a16, grouped by area as 0.1.0a15 was. The published## 0.1.0a15section and everything below it are byte-identical to thev0.1.0a15tag.docs/operations/upgrades.md: the alpha16 row and What changes in alpha16, with the measured migration times (0032: 17 s for 10,000 retained runs and 32 s for 50,000;0033: under 0.15 s on 10,000 and 50,000), upgrading CLIs and SDKs together with the server (newcall_completedevent andcallerfield, loop fields), upgrading the server before deployment runners, finishing or cancelling runs that use calls or loops before any rollback, and the contributor note for the acceptance journeys.docs/capabilities.mddescribes 0.1.0a16.Verification on this branch
All on macOS (Apple silicon, Python via uv, Node 26.3.0), first on the release branch after merging
mainat 3e0c251 (#53), then again after mergingmainat 900bbb1 (#57, follow-up fixes merged after the first merge). #57's four CHANGELOG entries were moved into their 0.1.0a16 groups; the published 0.1.0a15 section stays byte-identical to the tag.make check(scripts/check.py, 17 stages: source inventory, docs and strict MkDocs build, Ruff, format, mypy, unit and contract tests, both worker suites,prepare_release.py, installed-artifact verification)6854acf: 7,761 unit and contract tests, Agentic 222, Files 42 (7,751 on the first head); preparedfirefly_weave-0.1.0a16andweave_*_worker-0.1.8packagestests/unit/test_release_versions.pycheck_docs.py,source_coverage.py --stricton the final headnpm run check,format:check,npm test,npm run build6854acf(2,391 on the first head)scripts/build_studio.py)firefly-weave-studio-0.1.0a16.zipand.zip.sha256built; checksum verifiespytest tests/integration -n 4 --dist loadfile) against an owned PostgreSQL 17.11 oncolima-weave-tests(weave-rel-a16-pg, allocation 77, removed afterwards after an ID and label check)test-fixturesstage) the 24 provider inbox tests passed, and 5 timing-sensitive tests passed rerun alone (2 of 3 or better). Not run for lack of their services, as for L7 onmain: 57 Kafka, PostgreSQL connector target, CLI identity and release-image tests, plus the Keycloak and PostgreSQL TLS tests.test_parallel.py::test_two_replicas_join_once(known F50 load sensitivity; passed 2 of 2 alone for L7) failed alone 3 of 3 at a host load average of 41 to 99 from other sessions. This branch changes no code. After #57,test_human_tasks.py(changed by #57) passed 17 of 17 on a fresh owned PostgreSQL, also removed afterwards.scripts/acceptance.py --profile release --docker-context colima-weave-tests --subnet 10.246.77.0/24weave-rel-a16-r3on1fd0525: all six stages passed,complete: true, PostgreSQL 17 and Keycloak 26.7.4; 15 steps passed and 8 partial (later checks wait) across J0, J1, J5, J8 and J9; secret scan 0 hits in 216 files;resources_leftempty. r1 failed only because Playwright's headless shell 1193 was not installed, and its install stalls under Node 26, so r3 used the installed headless shell 1248 through the harness'sPLAYWRIGHT_CHROMIUM_EXECUTABLE. r2 timed out waiting for Keycloak under host load.make check-releaseAfter merge
Tag
v0.1.0a16on the merge commit onceChecks,Documentation,Desktop installersandAcceptanceare green for it, then build and audit the assets from the tag's workflow runs, draft, download back, publish and smoke the installer, as for 0.1.0a15 (ledgers/release-a15-publication.md).