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

Bump io.jstach.rainbowgum:rainbowgum-maven-parent from 0.8.0-SNAPSHOT to 0.8.0 #13

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Nov 18, 2024

Bumps io.jstach.rainbowgum:rainbowgum-maven-parent from 0.8.0-SNAPSHOT to 0.8.0.

Release notes

Sourced from io.jstach.rainbowgum:rainbowgum-maven-parent's releases.

v0.8.0

Feature Release

  • rainbowgum-jdk will load eagerly if it does not detect SLF4J. This was based on discussion #158 .

  • logging.systemlogger.initialize was also spelt incorrectly.

  • documentation improvements

What's Changed

Full Changelog: jstachio/rainbowgum@v0.7.1...v0.8.0

Changelog

Sourced from io.jstach.rainbowgum:rainbowgum-maven-parent's changelog.

Explanation

This project does not use the maven release plugin for a variety of reasons:

  • Creates an environment that can be very different from the normal snapshot deploy process by forking
  • Needlessly edits the pom file twice and checkins it in which requires every pom file in the project to be changed.
  • Because it constantly changes the SNAPSHOT pom on each release downstream projects have to remember to update their SNAPSHOT version even for patch releases.

Unlike the maven release plugin we do not constantly change the pom for each patch version. The release version is stored in a properties file called version.properties. The pom only should change (commited change) if the minor or major version changes.

For example say the pom is 0.7.0-SNAPSHOT and our last release is 0.6.0.

If we now want to make a patch version of 0.6.1 the pom file will not need to be updated (except by the release script for deployment). However if we are actually wanting to finally release 0.7.0 then the pom must be updated to something like 0.8.0-SNAPSHOT.

The vh script will mostly make sure you do not violate this.

Directions

Deploying SNAPSHOTs

If you just want to deploy a snapshot to centrals snapshot repositories run:

mvn clean deploy -Pcentral

Deploying Releases

Here is the process for release:

  1. Edit version.properties to the desired release version by calling:

  2. bin/vh set current NEW_VERSION

  3. If this is not a patch release you will need to update the pom to a later snapshot

  4. bin/vh set pom VERSION-SNAPSHOT # where VERSION is the new minor/major version

  5. Checkin the file version.properties (and pom file if minor or major version change). It will serve as the commit for tagging reproducible builds.

  6. run bin/vh release which will tag and temporarily update the pom for release. DO NOT CHECKIN THE ALTERED POM

  7. Run the commands it tells you to run

Updating Documentation

All the documentation should be in the aggregated javadoc. While sites like javadoc.io can host singular jars they cannot really host aggregate javadoc (e.g. mutltimodule).

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [io.jstach.rainbowgum:rainbowgum-maven-parent](https://github.com/jstachio/rainbowgum) from 0.8.0-SNAPSHOT to 0.8.0.
- [Release notes](https://github.com/jstachio/rainbowgum/releases)
- [Changelog](https://github.com/jstachio/rainbowgum/blob/main/release.md)
- [Commits](https://github.com/jstachio/rainbowgum/commits/v0.8.0)

---
updated-dependencies:
- dependency-name: io.jstach.rainbowgum:rainbowgum-maven-parent
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Nov 18, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Nov 27, 2024

Looks like io.jstach.rainbowgum:rainbowgum-maven-parent is no longer a dependency, so this is no longer needed.

@dependabot dependabot bot closed this Nov 27, 2024
@dependabot dependabot bot deleted the dependabot/maven/io.jstach.rainbowgum-rainbowgum-maven-parent-0.8.0 branch November 27, 2024 18:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants