chore: release v1.2.0 - #8
Merged
Merged
Conversation
Version bump for the access-config ownership fix and the pull-first policy reconcile merged in #7. Follows the v1.1.0 release precedent (package.json + README + docs/onboarding install refs). Also corrects the README status line's SDK reference: #7 moved the dependency to ^1.0.3, so the end-to-end verification claim now names the version it was actually made against.
zylos0t
approved these changes
Aug 28, 2026
zylos0t
left a comment
zylos0t
left a comment
There was a problem hiding this comment.
CLEAN at exact head 486a8fb. Reviewed release-only bump: package.json 1.1.0 -> 1.2.0, README/docs install refs v1.1.0 -> v1.2.0, README SDK text ^1.0.0 -> ^1.0.3. Existing tags stop at v1.1.0, so v1.2.0 is the next release slot. Package-lock remains at 1.1.0, matching this repo release precedent. CI is green; local npm test passed (42 tests).
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
2 participants
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.
What
Version bump
1.1.0→1.2.0for the changes merged in #7 (access-config ownership fix + pull-first policy reconcile).Touches the same three files as the
v1.1.0release precedent (chore: release v1.1.0 (#6)):package.json— versionREADME.md— status line +git clone --branchinstall refdocs/onboarding.md—git clone --branchinstall refWhy now
A bump is required before tagging:
v1.1.0already exists, and this repo is distributed bygit clone --branch v<version>, so the tag is the release artifact.Also
The README status line asserted verification against
@openmaxai/openmax-agent-sdk@^1.0.0. #7 moved the dependency to^1.0.3, so that reference now names the version the claim was actually made against. No other content changes.Test plan
Docs and metadata only, no code changes. CI (Quality Gate / Semgrep / Gitleaks) covers the tree as-is.