Skip to content

chore(main): release 1.15.0 - #515

Merged
mogul merged 1 commit into
mainfrom
release-please--branches--main
Oct 21, 2026
Merged

mogul merged 1 commit into
mainfrom
release-please--branches--main

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.15.0 (2026-10-21)

Features

  • acq-kits: add OpenDesign browser kit (#438) (83e202f)
  • isolation: define provider-neutral input contract (#518) (28a8ebd)
  • usai-catalog: refresh models and withhold undeployed gateway entries (#519) (03421e0)

Bug Fixes

  • usai-catalog: refuse a near-miss instead of enriching from the wrong model (#484) (c3a6dac)

This PR was generated with Release Please. See documentation.

@github-actions
github-actions Bot requested a review from a team as a code owner October 21, 2026 06:29
@github-actions github-actions Bot changed the title chore(main): release 1.14.1 chore(main): release 1.15.0 Oct 21, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch 2 times, most recently from 01e83bd to 7c3e1b2 Compare October 21, 2026 17:00
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch from 7c3e1b2 to 9789e25 Compare October 21, 2026 17:52
@mogul

mogul commented Oct 21, 2026

Copy link
Copy Markdown
Contributor

🤖 First Mate release handoff: this release contains merged provider-contract PR #518 at 28a8ebd, which is the immutable distribution boundary required to unblock GSA-TTS/agentic-coding-quickstart#600. The generated changelog correctly lists the contract under Features. No additional release-content changes are needed; approval and merge should publish v1.15.0.

@mogul
mogul requested a review from basiliskus October 21, 2026 17:55
@mogul

mogul commented Oct 21, 2026

Copy link
Copy Markdown
Contributor

🤖 First Mate blocker diagnosis: the only failed check is deterministic and release-specific. CHANGELOG.md links to compare/v1.14.0...v1.15.0, but release-please creates tag v1.15.0 only after this PR merges, so Link Check receives a pre-release 404. All other required checks pass and the PR is approved. A durable fix needs a narrow link-check exception for generated future-tag comparison links (or an equivalent release-PR workflow condition); rerunning this check before tag creation cannot make it pass.

@mogul
mogul merged commit f3c6acb into main Oct 21, 2026
6 of 7 checks passed
@mogul
mogul deleted the release-please--branches--main branch October 21, 2026 18:02
@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant