Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Releasing new version to forge #201

Open
sebastianberm opened this issue Sep 3, 2024 · 0 comments
Open

Releasing new version to forge #201

sebastianberm opened this issue Sep 3, 2024 · 0 comments

Comments

@sebastianberm
Copy link
Contributor

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 7.14
  • Ruby: 2.7
  • Distribution: Ubuntu 20.04
  • Module version: 3.2.0

What are you seeing

$ puppet module install puppet-borg
Notice: Preparing to install into /etc/puppetlabs/code/environments/production/modules ...
Notice: Downloading from https://forgeapi.puppet.com ...
Notice: Installing -- do not interrupt ...
/etc/puppetlabs/code/environments/production/modules
└─┬ puppet-borg (v3.2.0)
  ├── puppet-ssh_keygen (v4.1.0)
  ├─┬ puppet-systemd (v3.10.0)
  │ ├── puppetlabs-inifile (v4.4.0)
  │ └── puppetlabs-stdlib (v6.6.0)
  ├── puppetlabs-vcsrepo (v3.1.1)
  └── saz-ssh (v6.2.0)

What behaviour did you expect instead

Getting the latest version available (4.2.0), however, that version too does not contain the commit I need.

Any additional information you'd like to impart

Can you please tag a new version for the current HEAD of the master branch?
That way, I can do this correctly, instead of having to do a git checkout on our prod environment ;-).

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

No branches or pull requests

1 participant