Skip to content

(PA-7824) Use newest Bolt#829

Merged
mhashizume merged 2 commits into
mainfrom
PA-7824/main/update-bolt
May 4, 2026
Merged

(PA-7824) Use newest Bolt#829
mhashizume merged 2 commits into
mainfrom
PA-7824/main/update-bolt

Conversation

@mhashizume
Copy link
Copy Markdown
Contributor

This commit removes the pin for puppet_litmus in the Gemfile and adds both PuppetCore credentials and the PUPPET_FORGE_TOKEN env var in order to use puppet_litmus > 2, which uses newer (~> 5) versions of Bolt.

@mhashizume mhashizume force-pushed the PA-7824/main/update-bolt branch from 65ea3b5 to 11a6192 Compare April 23, 2026 22:13
@mhashizume mhashizume marked this pull request as ready for review April 24, 2026 03:19
@mhashizume mhashizume requested review from a team and bastelfreak as code owners April 24, 2026 03:19
This commit updates the Gemfile to always use the latest major version
of puppet_litmus, even when the PUPPET_FORGE_TOKEN env var is not
present, so that we can always use the latest Bolt.

We do not want to control whether we use the latest bolt with that env
var because we want to be able to use unreleased Puppet 9 nightly gems
from an internal Artifactory instance instead of from public Puppet Core
repos (from which Puppet 9 nightlies are currently unavailable).
@mhashizume mhashizume merged commit 7b8e24e into main May 4, 2026
9 checks passed
@mhashizume mhashizume deleted the PA-7824/main/update-bolt branch May 4, 2026 17:54
@mhashizume mhashizume added the enhancement New feature or request label May 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants