Bump versions forensics-api, plugin-util-api, and checks-api #1513
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Freeze version to 1.7.5 for 2.332 and lower.
# Conflicts: # bom-weekly/pom.xml
|
@uhafner thanks for allowing push to this branch. I've reached a point where I don't understand what additional steps can be taken to make this pull request pass or to make #1521 pass. Can you offer any insights of changes that are needed? My puzzlement is described in #1521 (comment) @jglick and @timja I believe that the plugin bill of materials is at a point where it is ready to release a new version. Is that done by someone labeling a merged pull request with "developer" or is there a better technique? |
|
Or retroactively, by manually triggering the release workflow when the current trunk commit has a green check. |
Bumps `plugin-util-api.version` from 2.17.0 to 2.20.0. Updates `plugin-util-api` from 2.17.0 to 2.20.0 - [Release notes](https://github.com/jenkinsci/plugin-util-api-plugin/releases) - [Changelog](https://github.com/jenkinsci/plugin-util-api-plugin/blob/master/CHANGELOG.md) - [Commits](jenkinsci/plugin-util-api-plugin@v2.17.0...v2.20.0) Updates `plugin-util-api` from 2.17.0 to 2.20.0 - [Release notes](https://github.com/jenkinsci/plugin-util-api-plugin/releases) - [Changelog](https://github.com/jenkinsci/plugin-util-api-plugin/blob/master/CHANGELOG.md) - [Commits](jenkinsci/plugin-util-api-plugin@v2.17.0...v2.20.0) --- updated-dependencies: - dependency-name: io.jenkins.plugins:plugin-util-api dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: io.jenkins.plugins:plugin-util-api:tests dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps `checks-api.version` from 1.8.0 to 1.8.1. Updates `checks-api` from 1.8.0 to 1.8.1 - [Release notes](https://github.com/jenkinsci/checks-api-plugin/releases) - [Commits](jenkinsci/checks-api-plugin@v1.8.0...v1.8.1) Updates `checks-api` from 1.8.0 to 1.8.1 - [Release notes](https://github.com/jenkinsci/checks-api-plugin/releases) - [Commits](jenkinsci/checks-api-plugin@v1.8.0...v1.8.1) --- updated-dependencies: - dependency-name: io.jenkins.plugins:checks-api dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: io.jenkins.plugins:checks-api:tests dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
# Conflicts: # bom-weekly/pom.xml
…ecks-api.version-1.8.1' into js-libs
…ugin-util-api.version-2.20.0' into js-libs
uhafner
changed the title
This was referenced Dec 19, 2022
# Conflicts: # bom-weekly/pom.xml
jglick
added
developer
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Replaces: