chore: prepare v0.8.0 release metadata#84
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
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 the
v0.8.0release branch by cutting the Apex release notes into the changelog, bumping package metadata to0.8.0, and aligning contributor/support docs with the current protected-branch release workflow.Changes
package.jsonandpackage-lock.jsonfrom0.7.0to0.8.0CHANGELOG.mdas## [0.8.0] - 2026-05-14and advance compare linksAGENTS.mdandSECURITY.mdso release guidance, language/support coverage, and protected-branch workflow match the current repo stateTesting
How were these changes tested?
npm run build)npm run typecheck)npm run test:run)npm run lint)Release Labels
feature,bug,performance,documentation,dependencies,refactor,test,chore, orskip-changelog)semver:major,semver:minor,semver:patch) when neededRelated Issues