Repository navigation
Release 6.0.0 - #570
Merged
Merged
Release 6.0.0#570
Conversation
The six reactor poms and the standalone agent pom at 6.0.0 (versions:set also moved project.build.outputTimestamp), the CHANGELOG heading [6.0.0] - 2026-10-25 with a fresh [Unreleased] and the compare links, SECURITY.md supporting 6.x. The README's release snippets were already at 6.0.0; its snapshot line stays 6.0.0-SNAPSHOT until the post-release bump. TODO: the release section after the snapshot dispatch 40227501358. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VszvDmRRPP1UcwozsUMY1L
bernardladenthin
had a problem deploying
to
maven-central
October 25, 2026 21:46 — with 
GitHub Actions
Failure
GitHub Actions
Failure
bernardladenthin
had a problem deploying
to
startgate
October 25, 2026 21:46 — with
GitHub Actions
Error
GitHub Actions
Error
bernardladenthin
had a problem deploying
to
maven-central
October 25, 2026 21:46 — with
GitHub Actions
Failure
GitHub Actions
Failure
|
Caution Review failedThe pull request is closed. Finishing Touches
Comment |
|
This branch had an error being deployed
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.
The release commit for 6.0.0 (workspace release procedure, step 1; supplement
docs/RELEASE.md).mvn versions:set -DnewVersion=6.0.0, which also movedproject.build.outputTimestampin the root pom) and inllama-atmosphere-agent/pom.xmlby hand.## [6.0.0] - 2026-10-25under a fresh empty[Unreleased]; footer[6.0.0]: …/compare/v5.1.0...v6.0.0,[Unreleased]nowv6.0.0...HEAD. The date is today's -- adjust it if the tag lands later. Headings and footer links agree (6.0.0 5.1.0 5.0.6 … 5.0.0).examples/jbang/Chat.java,examples/server/pom.xml, the agent README) were already at6.0.0. The README's snapshot line (README.md:191) stays6.0.0-SNAPSHOTon purpose; it moves to the next snapshot with the post-release bump (step 3).github-snapshot(403 moving thesnapshottag with the workflow token) andcentral-snapshot(a GitHub API 502) failed, neither on the release path -- both go into actions v1.0.3.Local checks:
check-natives.py0 disagreements (the agent pom equals the reactor), publication wiring 0 problems, templates 0 problems.After the merge (owner): tag
v6.0.0on the merge commit and dispatch Publish on the tag withpublish_to_central=true. The tag push starts a second, non-publishing run that is not cancelled automatically; the tag build is uncached (expect 4-5 h).🤖 Generated with Claude Code
https://claude.ai/code/session_01VszvDmRRPP1UcwozsUMY1L