Skip to content

chore(release): release 1 plugins #9535

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
melodic-plugin-release merged 1 commit into from
Oct 24, 2026
Merged

chore(release): release 1 plugins #9535

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 0 additions & 7 deletions .changes/pr-pipeline/perf-9473-head-ref-map-carry-3f9a6c21.md
View file
Open in desktop

This file was deleted.

6 changes: 6 additions & 0 deletions docs/conventions/pr-pipeline/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,11 @@
# Changelog for the PR pipeline convention

## [4.14.1] - 2026-10-24

### Changed

- pr-merge's head-ref map (`.github/scripts/pr-merge/head-ref-map.mjs`) is carried on a run that saves no artifact listing, such as a run with no candidates: the map read before the gate is uploaded as it is, with one log line and no warning, and the next run that saves a listing prunes it. Before, that run warned and uploaded no map, so once the trusted-run window passed the next run downloaded every untied FAIL again. A listing file that exists but cannot be read still uploads nothing, and with no map read before the gate nothing is uploaded. The map is still read only from the newest scheduled or hand-started `pr-merge.yml` run on main and never passes through `actions/cache`.

## [4.14.0] - 2026-10-24

### Changed
Expand Down
Loading