Skip to content

chore(master): release 1.19.1 - #409

Merged
mlorentedev merged 2 commits into
masterfrom
release-please--branches--master
Oct 10, 2026
Merged

mlorentedev merged 2 commits into
masterfrom
release-please--branches--master

Conversation

@mlorentedev

@mlorentedev mlorentedev commented Oct 2, 2026 •

Copy link
Copy Markdown
Owner

🤖 I have created a release beep boop

1.19.1 (2026-10-09)

Bug Fixes

  • ci: close the doc auth-key guard bypasses found in review (#421) (ec34eb7)
  • ci: move PR-Agent off the retired mimo-v2.5 model (#413) (177355c)
  • ci: stop check-lessons reporting indexed lessons as missing (#419) (b098987)
  • init: require a control plane for Headscale keys (#406) (cea8341)

This PR was generated with Release Please. See documentation.

@coderabbitai

coderabbitai Bot commented Oct 2, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Important

Review skipped

Review was skipped as selected files did not have any reviewable changes.

⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 71812419-c25f-4d07-8c08-890159481d82

📥 Commits

Reviewing files that changed from the base of the PR and between 823de14 and ee97181.


You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 9286924f-d2ab-460d-858d-d95cf5b1e408

📥 Commits

Reviewing files that changed from the base of the PR and between 5fc1d8c and 823de14.


📒 Files selected for processing (2)
  • .release-please-manifest.json
  • CHANGELOG.md

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.



📝 Walkthrough

Walkthrough

The root package version changes from 1.19.0 to 1.19.1. The changelog adds a dated 1.19.1 entry with four bug-fix notes.

Changes

Release metadata

Layer / File(s) Summary
Version and release notes
.release-please-manifest.json, CHANGELOG.md
The manifest sets the root package version to 1.19.1. The changelog adds a 1.19.1 entry dated 2026-10-09 and lists four bug fixes.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other


Merge Risk: ⚪ Minimal · up to 823de

The release metadata records version 1.19.1 and its listed fixes; no actionable merge-blocking risk is identified.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check Warning The description provides release notes and bug-fix details, but it does not use the required Summary, Changes, Testing, and Type sections. It also does not report testing results or select a change ty… Add the required template sections. Summarize the release under Summary, list the release changes under Changes, report the testing results under Testing, and select the chore type under Type.
✅ Passed checks (4 passed)
Check name Status Explanation
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Title check Passed The title clearly identifies the maintenance release and version 1.19.1. It matches the primary change in the pull request.

Full details: Description check

Explanation

The description provides release notes and bug-fix details, but it does not use the required Summary, Changes, Testing, and Type sections. It also does not report testing results or select a change type.


✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@mlorentedev
mlorentedev force-pushed the release-please--branches--master branch 7 times, most recently from 551dcc8 to 823de14 Compare October 9, 2026 16:45
@mlorentedev
mlorentedev force-pushed the release-please--branches--master branch from 823de14 to 75ba202 Compare October 9, 2026 16:52
@mlorentedev

Copy link
Copy Markdown
Owner Author

Review triage

Item Disposition Reason
CodeRabbit review of .release-please-manifest.json and CHANGELOG.md up to 823de14 skip The reviewed release metadata had no actionable code findings. The current regenerated head is 75ba202, so this older review is not claimed as coverage of the current head.
CodeRabbit description-check warning skip Release-please generates the release notes as this PR body; the repository's release-please exemption explicitly distinguishes it from an agent-authored PR that uses the standard template. No source change is indicated.
Current-head CI skip Required test, Windows test, smoke, lint, security and six build-matrix jobs are green at 75ba202; the review job is intentionally skipped for this release class.

Reviewer output dispositioned: coderabbitai[bot], 2026-10-02T20:23:01Z. This does not authorize merging #409; it remains open for the operator's release decision and current-head review.

@mlorentedev
mlorentedev merged commit 107ff2f into master Oct 10, 2026
15 checks passed
@mlorentedev
mlorentedev deleted the release-please--branches--master branch October 10, 2026 18:45
@mlorentedev

Copy link
Copy Markdown
Owner 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