Skip to content

DEV-1393: put the Java HIL first in the release steps - #342

Merged
JongChern merged 1 commit into
masterfrom
DEV-1393_release_needs_hil
Nov 16, 2026
Merged

JongChern merged 1 commit into
masterfrom
DEV-1393_release_needs_hil

Conversation

@JongChern

Copy link
Copy Markdown
Contributor

release.yml stops before building unless the commit has a passing java-hil status (or hil_waiver names a Jira key), but the Releasing steps in AGENTS.md didn't mention it. An agent reading them learned it only when the release refused.

This adds it as step 1, pointing to "Before every Java API release" in tools/hil/README.md, and says to run it after the last merge. The later steps are renumbered and otherwise unchanged.

Docs only. Merging moves master, so the next release needs a HIL run at the new commit anyway.

🤖 Generated with Claude Code

release.yml stops before building unless the commit has a passing java-hil
status, but AGENTS.md's Releasing steps didn't mention it, so an agent
learned it only when the release refused. Add it as step 1, pointing to the
gate section of tools/hil/README.md.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

@jyong15 jyong15 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good

@JongChern
JongChern merged commit 815869c into master Nov 16, 2026
2 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.

2 participants