Skip to content

release: v0.0.112, pinning core v0.7.1 - #78

Merged
antoinetoussaint-byte merged 1 commit into
mainfrom
release-0.0.112
Sep 30, 2026
Merged

antoinetoussaint-byte merged 1 commit into
mainfrom
release-0.0.112

Conversation

@antoinetoussaint-byte

Copy link
Copy Markdown
Contributor

Re-pins from core v0.6.0 to v0.7.1 and bumps the manifest to 0.0.112, in one commit.

This agent last released against v0.5.1, so it was two minor versions behind. v0.7.1 carries a4bd744c ("a deployed environment gets a profile of its own, and an owed value fails the render") plus ten closed dependency advisories.

The re-pin and the bump are together deliberately: a version bump alone cuts a tag on the old core and needs a second release immediately after — which happened to a sibling agent this round.

go build ./... passes on the new pin.

Not verified: agent CI against the new core is this PR's job; no cluster or registry behaviour was exercised locally. The output-limit alias question from #77 is untouched here and stays open.

🤖 Generated with Claude Code

Last released against core v0.5.1 and main had moved only to v0.6.0, so this
agent was two minor versions behind. v0.7.1 carries a4bd744c ("a deployed
environment gets a profile of its own, and an owed value fails the render")
plus ten closed dependency advisories.

Re-pin and version bump in one commit: bumping the manifest alone cuts a tag
on the old core and needs a second release straight after, which is what
happened to a sibling agent this round.

`go build ./...` passes on the new pin.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@antoinetoussaint-byte
antoinetoussaint-byte merged commit 83dc764 into main Sep 30, 2026
7 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant