Repository navigation
chore(release): prepare 0.6.0 - #21
Merged
Merged
Conversation
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
1 participant
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.
Summary
Prepare version 0.6.0 for the Forward Drive Beta APIs and Template
managed_tool_configsupport already merged into main. Move the release notes fromUnreleasedto0.6.0, leaving an emptyUnreleasedsection.Why
Align the SDK version, release notes, and release instructions before the version-tagged GitHub release workflow runs.
Update
package.json, both root versions inpackage-lock.json,src/version.ts, the generated VERSION API page, and the release command example. Dependency versions remain unchanged.Verification
npm run typechecknpm test(includes build and type tests): 3,751 tests passednpm run docs:checknpm pack --dry-run --jsonLive integration tests and business examples were not rerun for this metadata-only change.
Impact
No runtime API or contract fixture changes in this PR. The generated VERSION page matches the source, and the existing Drive and Template entries are preserved in the 0.6.0 changelog. Go and Python release preparation uses the same version and release notes. No credentials or generated test output are included.