Repository navigation
Release flow: main only, tagged releases, pkgdown deployment - #18
Merged
Merged
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
hypebright
changed the title
hypebright
marked this pull request as ready for review
November 4, 2026 08:18
This was referenced Nov 4, 2026
Draft
Pins the third-party actions in ci.yaml to the commits their current tags point to (CodeQL actions/unpinned-tag). Dependabot keeps them up to date with one grouped PR per month. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
4 of 5 tasks
tkranenburgrivm
approved these changes
Nov 9, 2026
ro_check_if_font_available() was not formatted, so the air-format CI job failed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Collaborator
Author
|
@tkranenburgrivm FYI: I added one commit that only formats |
Pin third-party GitHub Actions to commit SHAs, add Dependabot
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
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.
Closes #10. Part of rivm-syso/ROvis#23, which has the review order and merge steps.
📘 What is this PR about?
Implements the agreed release flow in
ROvis.utils. The PRs in the other six repos make the same change, so this is the one to review in full..github/workflows/release.yaml(new): on a push tomainwith a release version (no.9000) that has no tag yet, it creates tagvX.Y.Zand a GitHub release with theNEWS.mdsection as notes, then opens a PR that setsX.Y.Z.9000.ci.yaml: pkgdown job re-enabled, unchanged from the commented-out version._pkgdown.yml:url:set, plusdevelopment: mode: auto: releases build the site root,.9000versions build/dev/.DESCRIPTION:URL:andBugReports:.Versionstays0.1.0.NEWS.md: heading# ROvis.utils v0.1.0→# ROvis.utils 0.1.0, the formatusethisandrelease.yamlread.README.md: install from R-universe (release) and GitHub (development).CONTRIBUTING.md: new "Releases" section.✅ Checklist
CONTRIBUTING.md🧪 How to test / verify
Only testable on GitHub, after the merge:
v0.1.0and a GitHub release exist, and a PR "Increment version number to 0.1.0.9000" is open./dev/.ℹ️ Extra info
v0.1.0. Merge only after the branch rename (step 3 in Release flow and pkgdown websites ROvis#23).