Skip to content

feat(scripts): push downgrades only when allowed - #48

Merged
noctuum merged 1 commit into
mainfrom
allow-downgrade
Oct 21, 2026
Merged

noctuum merged 1 commit into
mainfrom
allow-downgrade

Conversation

@noctuum

@noctuum noctuum commented Oct 21, 2026

Copy link
Copy Markdown
Member

A downgrade reaches the AUR only when the package YAML sets allow_downgrade: true. Without it, check-all.sh writes downgrade_skipped: <version>, pushes nothing and opens no issue. --prepare and --publish apply the same rule, and --publish keeps the status the check run wrote. The status table shows ⬇️ <version> skipped (downgrade), and validate-pkg.sh accepts only a boolean for the new field.

GitHub picks /releases/latest by the date of the commit a release was made from, so a maintenance release of an older line can become the latest release. README.md and docs/WORKFLOW.md describe the new default.

Without allow_downgrade: true, a lower version gets downgrade_skipped.
@codecov

codecov Bot commented Oct 21, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@noctuum
noctuum merged commit b56f7eb into main Oct 21, 2026
5 checks passed
@noctuum
noctuum deleted the allow-downgrade branch October 21, 2026 00:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant