Releases: BootstrapLaboratory/rush-delivery
Releases · BootstrapLaboratory/rush-delivery
Rush Delivery v0.7.1
Security maintenance patch for website and documentation tooling dependencies.
Fixed
- Updated Astro site dependencies to resolve OSV advisories for
astro,devalue, andfast-uri. - Updated Docusaurus site dependencies to resolve OSV advisories for Babel SystemJS transform tooling and
fast-uri. - Updated root Yarn resolution for
fast-urito the patched version.
Notes
No Rush Delivery public API, metadata schema, workflow behavior, or Dagger module behavior changed in this release.
Rush Delivery v0.7.0
Rush Delivery v0.7.0
This release makes package release a first-class part of the main Rush Delivery workflow.
Added
- Added
release-targets-jsonto theworkflowentrypoint. - Added GitHub Action support for composed package release through:
release-targets-jsonworkflow-envworkflow-env-file
- Added shared workflow env handling, with
deploy-envandrelease-envkept as scoped overlays. - Added workflow composition for npm package release targets.
- Added
schemas/v0.7.0and updated current documentation/examples tov0.7.0.
Changed
workflowcan now run deploy targets and npm package release targets from one shared source/build lifecycle.- When
release-targets-json: '["npm"]'is selected, Rush Delivery runs the all-project Rush lifecycle once, then runs deploy and package release side effects after shared prerequisites pass. - Deploy-only workflows keep their existing behavior when no release targets are selected.
Notes
Deploy and npm publish side effects are coordinated but not transactional. If both are selected and one succeeds while the other fails, external side effects may already have happened.
Rush Delivery v0.6.7
What's Changed
Rush Delivery v0.6.7 is a release-line update for Daggerverse metadata and Dagger engine alignment.
- Added module descriptions for Daggerverse so the module page shows useful summary text.
- Updated the Dagger engine requirement to
v0.20.7. - Published
v0.6.7docs and schema URLs for exact-version references. - Archived
v0.6.6docs as the previous release line.
Compatibility
- No Rush Delivery metadata contract behavior changed.
v0.6.7schema snapshots are published for version alignment; they do not introduce new schema requirements.
Validation
npm run typechecknpm testnpm run site:docusaurus:checknpm run site:checkdagger --silent -m . call self-check
Rush Delivery v0.6.6
Fixes
- Fixed
releasePackagesin Git source mode by preparing the localversioning.target_branchbefore invokingrush publish. - This allows Rush to complete its generated version commit flow after npm packages are published, including the final target-branch checkout/merge/push step.
Docs
- Updated README, docs, website examples, and schema links for
v0.6.6. - Added the
v0.6.6schema snapshot. - Archived
v0.6.5documentation for the versioned Docusaurus site.
Rush Delivery v0.6.5
Fixes
- Made the npm provenance contract explicit:
publish.provenancedefaults tofalseand provenance is opt-in. - Added regression coverage for
.dagger/release/npm.yamlfiles that definepublish:withoutprovenance.
Docs
- Documented why provenance should usually stay omitted/false in the default Dagger-contained release flow.
- Updated examples and schema links to
v0.6.5. - Added the
v0.6.5schema snapshot and archivedv0.6.4Docusaurus docs.
Rush Delivery v0.6.4
Fixes
- Fixed
release-packagesGit authentication order. - Rush Delivery now configures authenticated Git remote access before running
rush publish, allowing Rush’s internalpublish-*branch push to succeed. - Removed the redundant post-publish Git push from Rush Delivery’s release execution plan and lets Rush own the publish branch, merge, tag push, and cleanup flow.
Docs
- Updated examples and schema links to
v0.6.4. - Added
v0.6.4schema snapshot. - Archived
v0.6.3documentation.
Rush Delivery v0.6.3
Fixes
- Fix
release-packagesfailing duringrush publishbecause internal Rush Delivery Git auth variables used the reservedRUSH_prefix. - Move token-backed Git push auth setup to run after
rush publish, right beforegit push. - Keep Git author identity setup before
rush publishso Rush can still create the version commit.
Docs
- Updated current docs and examples to
v0.6.3. - Added
schemas/v0.6.3for exact schema pinning. - Archived
v0.6.2docs in the Docusaurus versioned docs site.
Verification
npm testnpm run typechecknpm run site:docusaurus:checknpm run site:check
Rush Delivery v0.6.2
Fixes
- Run the shared Rush lifecycle in build-first order:
build,lint,test,verify. - Fixes package release flows where
rush verifyor tests import sibling workspace packages whose build outputs do not exist yet. - Keeps the public module API unchanged.
Docs
- Updated current docs and examples to
v0.6.2. - Added
schemas/v0.6.2for exact schema pinning. - Archived
v0.6.1docs in the Docusaurus versioned docs site.
Verification
npm testnpm run typechecknpm run site:docusaurus:checknpm run site:check
Rush Delivery v0.6.1
v0.6.1
Patch fix for package-only release workflows.
Fixed
release-packagesnow uses release-scoped metadata validation.- Package-only repositories no longer need deploy metadata such as
.dagger/deploy/services-mesh.yaml. .dagger/rush-cache/providers.yamlis only required whenrush-cache-provideris enabled.rush-cache-provider: offno longer attempts to read Rush cache provider metadata.
Docs
- Added
schemas/v0.6.1/schema URLs. - Updated current docs and examples to
v0.6.1. - Archived
v0.6.0docs.
Rush Delivery v0.6.0
v0.6.0
Adds the first package release stage for npm packages.
Added
- New
releasePackages/release-packagesentrypoint. - New
.dagger/release/npm.yamlmetadata contract. - New
npm-release.schema.jsonandschemas/v0.6.0schema snapshot. - GitHub Action support for
release-envandrelease-env-file. - PR release-readiness validation through Rush change verification.
Notes
- The standalone release flow creates the Rush version/publish commit and pushes it through Git source mode.
- Deploy tags are intentionally not touched by this first release flow.