chore: force release version to 7.2.0 - #556
Merged
Merged
Conversation
Several commits merged into main's history via #554 (the 6.x-into-main merge) carried breaking-change markers (feat(agent)!: and BREAKING CHANGE: footers) for real interface changes in nullplatform/agent and service_definition_agent_association. That's causing release-please to compute the next version as 8.0.0 (PR #555). These changes are being treated as non-breaking for this repo's consumption model: every consumer pins an exact `?ref=vX.Y.Z` per module, so no automatic upgrade behavior depends on strict semver correctness here. The actual interface changes remain fully documented in each commit's body — only the version-bump signal is being overridden. Release-As: 7.2.0
gdrojas
approved these changes
Sep 3, 2026
release-application Bot
added a commit
that referenced
this pull request
Sep 3, 2026
🤖 I have created a release *beep* *boop* --- ## [7.2.0](v8.0.0...v7.2.0) (2026-09-03) ### Miscellaneous Chores * force release version to 7.2.0 ([#556](#556)) ([3abfc8c](3abfc8c)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
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.
Summary
#554 (the 6.x-into-main merge) included three commits carrying breaking-change markers for real interface changes in
nullplatform/agentandservice_definition_agent_association. That's causing release-please to compute the next version as8.0.0(see PR #555, already open).These changes are being treated as non-breaking for this repo's consumption model: every consumer pins an exact
?ref=vX.Y.Zper module, so no automatic upgrade behavior depends on strict semver correctness here. This PR doesn't touch any file — it's an empty commit carrying aRelease-As: 7.2.0footer, release-please's documented mechanism for overriding the computed version.Once merged, release-please should regenerate #555 (or open a new release PR) targeting
7.2.0instead of8.0.0.🤖 Generated with Claude Code