Release v1.10.1#48
Closed
mavam wants to merge 1 commit into
Closed
Conversation
Move the project fixture inline dependency changelog entry into the v1.10.1 release, add release notes, and bump the package metadata. AI-Assisted-By: Codex
Member
Author
|
Closing this release PR because the failed release workflow needs discussion before changing the release path. |
auto-merge was automatically disabled
May 13, 2026 12:57
Pull request was closed
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
1 participant
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.
🔍 Problem
The v1.10.1 release cannot be published directly from the release workflow because
mainrequires changes to land through a pull request.🛠️ Solution
💬 Review
Focus on the generated release metadata and version bump. After this PR merges, rerun the release workflow to publish the tag and GitHub release.