Skip to content

chore(main): release 1.1.2#28

Merged
OgeonX-Ai merged 1 commit into
mainfrom
release-please--branches--main
Jul 13, 2026
Merged

chore(main): release 1.1.2#28
OgeonX-Ai merged 1 commit into
mainfrom
release-please--branches--main

Conversation

@OgeonX-Ai

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.1.2 (2026-07-13)

Bug Fixes

  • ci: repin release-please reusable workflow to reachable SHA (#23) (3029fbe)
  • ci: wire release-please PAT into reusable workflow caller (#27) (d15cc54)
  • registry: rewrite schema $id to the resolvable Pages registry URL (#18) (b385f15)

This PR was generated with Release Please. See documentation.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 90bfb70bc6

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread CHANGELOG.md

All notable changes follow Semantic Versioning and Keep a Changelog conventions.

## [1.1.2](https://github.com/Coding-Autopilot-System/cas-contracts/compare/v1.1.1...v1.1.2) (2026-07-13)

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Do not publish the breaking ID change as a patch

Because this release includes the schema $id rewrite listed below, shipping it as 1.1.2 is not semver-safe: the same changelog still explicitly marks that $id migration as BREAKING for consumers such as offline validators that hardcode the old ID, and docs/VERSIONING.md reserves consumer-breaking public API changes for a major release. If this tag is cut, semver-following consumers can auto-upgrade within 1.1 and lose schema resolution; cut a major release or exclude/revert the breaking change from this patch.

Useful? React with 👍 / 👎.

@OgeonX-Ai
OgeonX-Ai merged commit 64e846a into main Jul 13, 2026
5 checks passed
@OgeonX-Ai
OgeonX-Ai deleted the release-please--branches--main branch July 13, 2026 10:24
@OgeonX-Ai

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