Skip to content

[On hold] Release flow: main only, tagged releases, pkgdown deployment - #26

Draft
hypebright wants to merge 1 commit into
developfrom
18-release-strategy
Draft

hypebright wants to merge 1 commit into
developfrom
18-release-strategy

Conversation

@hypebright

Copy link
Copy Markdown
Collaborator

Important

Draft, on hold. Not ready for review until the open ROvis.echarts PRs #14, #24 and #25 are merged. This branch will then be rebased.

Closes #18. Part of rivm-syso/ROvis#23, which has the review order and merge steps.

📘 What is this PR about?

Same change as rivm-syso/ROvis.utils#18: review that one first. release.yaml, ci.yaml and the "Releases" section in CONTRIBUTING.md are identical to it.

Only in this repo:

  • Remotes: → rivm-syso/ROvis.utils@*release, replacing git@github.com:rivm-syso/ROvis.utils (that form needs an SSH key).

✅ Checklist

  • I have read contributing guidelines at CONTRIBUTING.md
  • My code follows the style guidelines of this project
  • I have tested these changes and added tests (if applicable)
  • I have added necessary documentation / comments
  • I have linked relevant issues

🧪 How to test / verify

Same as rivm-syso/ROvis.utils#18, after the merge.

ℹ️ Extra info

Same change as rivm-syso/ROvis.utils#18: release.yaml, pkgdown job
re-enabled, pkgdown development mode, URL/BugReports, usethis NEWS
heading, install instructions and a Releases section in CONTRIBUTING.md.
Remotes entries point at the latest release (@*release).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Comment thread .github/workflows/ci.yaml Resolved
Comment thread .github/workflows/ci.yaml Resolved
Comment thread .github/workflows/ci.yaml Resolved

This branch has not been deployed

No deployments
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.

Re-enable pkgdown deployment

2 participants