| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
The release process should not create 1.31.0-SNAPSHOT? That's fine if so. I just ask because I know some of our other release processes never commit non-SNAPSHOT versions to head so I want to make sure that isn't the case here.
Sorry, something went wrong.
|
@elharo, this PR changes everything from -SNAPSHOT to the latest version (1.31.0), unless I'm missing something you're seeing, can you share a link? |
Sorry, something went wrong.
|
Yes, and my question is whether we want to do that? Some release processes jump straight from 1.30.2-SNAPSHOT to 1.31.0-SNAPSHOT when releasing 1.30.2 and have the non-SNAPSHOT version only on branches. But it sounds like that's not how yoshi works? |
Sorry, something went wrong.
|
@elharo We have one commit in master that has the non snapshot which is tagged for the release (rather than a long lived branch). The next commit is a snapshot bump. |
Sorry, something went wrong.
Sorry, something went wrong.
|
The release build has started, the log can be viewed here. 🌻 |
Sorry, something went wrong.
|
🥚 You hatched a release! The release build finished successfully! 💜 |
Sorry, something went wrong.
…#754) * disabling self-signed jwt for domain wide delegation * fix: nit fixes
| Back | FazBrowse Home | New Git URL |
This pull request was generated using releasetool.
07-31-2019 07:21 PDT
Implementation Changes
New Features
Dependencies
Documentation
Internal / Testing Changes