Repository navigation
v1.0.0 #154
Unanswered
froggleston
asked this question in
Q&A
v1.0.0
#154
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
This release fundamentally changes how the renv caching steps work, by moving away from GH/AWS S3 caches (which require elevated permissions) to docker dependency layer caches published to GitHub's package repository, GHCR.io.
The reasons for doing so are due to recent breaking changes in restricting permissions for
pull_requesttriggered workflows (e.g. in "03 Maintain: Apply Package Cache" and "Bot: Receive Pull Request").These changes meant that the default GITHUB_TOKEN could no longer be used to access credentials or manage PRs when automatically triggered by certain action triggers.
The new docker layer builds on the base workbench-docker image, and stores the R packages installed by renv during the 03 Apply workflow.
The published dependency image layer can be used both by the workflows for subsequent builds, but also by the community in their own environments so they get a fully reproducible build of the lesson at a given point in time (including all packages).
What Else Has Changed
Full Changelog: v0.18.0...v1.0.0
This discussion was created from the release v1.0.0.
All reactions