v6.0.1 (2020-10-06)
- Add support for Puppet Forge API keys
- Add the full license text
- Require puppet-modulebuilder ~> 0.2
- Drop old ruby code
- We had some code for Ruby 2.0 in the Gemfile. Since we require Ruby 2.4, we can drop the old code
- Forge upload should always use namespace
There is an author field in metadata.json, but pdk build
always uses
the module's namespace when building the tarball. Therefore, Blacksmith
should do the same and not even use the author field.
This module moves from puppetlabs_spec_helper's build
rake task to its own module:build
task which uses puppet-modulebuilder. This has the benefit that it no longer needs the Puppet face (Puppet < 6) or the PDK (Puppet >= 6) and becomes standalone.
- Use puppet-modulebuilder to build modules
- Enable Artifactory access via API key. This provides an additional authentication mechanism besides a password
- Remove outdated variable reference. This fixes a regression in Artifactory upload exception handling
Note: The gemspec got updated to require at least Ruby 2.4 or newer. Older versions are end of life and unsupported.
- Add note about clearing the rake task cache
- Add support for Artifactory uploads
- Update the maximum allows puppet versions
- Update description for module:release task
- Factor out uploading to separate functions
- Handle RC versions while patching
- Improve testing code
- Fix an incorrect checksum on rubygems
- Expose
tag_sign
option in the RakeTask
- Allow creating signed tags
This version is a fixup release since the 4.0.0 release broke the CI of a user which was still using Ruby 1.9.3.
- Require ruby >= 2.0.0 in the gemspec
This version drops Modulefile support. Upstream Puppet has removed the support from the code and we used that. It means we no longer use the Puppet gem which greatly reduces the profile of the module.
- Add has_tag? and has_version_tag? methods
- Make exec_git a private method
- Support Ruby 2.2 - 2.4
- Rip out Modulefile support
- Allow using newer rest-client and webmock versions
- Handle spaces in git paths
- Allow creating annotated git commits
- Make commit message configurable
- Fix rake module release order
- Drop ruby 1.9 support
- Pin rest-client and webmock for ruby 1.9 support
- Add 'version', 'version:next' and 'version:next:[patch|major|minor]'
- Allow loading forge credentials from project dir
- Add bump_commit commands for patch, minor, major and full
- Allow setting credentials via env vars
- Add bump:full rake task
bump:*
runs twice if task is defined inRakefile
- Allow releasing without building nor pushing to the forge, just git tagging [:clean, :tag, :bump_commit], using
build = false
- Enable bumping semantic version elements with
module:bump:
pluspatch
,minor
,major
- Added feature to bump dependencies
module:dependency[modulename, version]
- Add support for custom tag patterns
- Issue #9 Better error messages when pushing to the Forge fails
- Fix uninitialized constant Blacksmith::VERSION
- Use API to upload to the Forge instead of parsing the webpage
- Use a custom Blacksmith
User-Agent
- Issue #7
module:bump_commit
fails ifModulefile
does not exist
- Issue #6 Add support for
metadata.json
- Support Puppet 3.5+
- Reworked to be a library plus rake tasks so it an be reused
.puppetforge.yml
forge
entry is deprecated, useurl