ci: automatically bump the Frank!Framework version on a weekly basis #301
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
added 18 commits
April 17, 2024 00:26
…ated any ff version instead of only latest
added 10 commits
April 22, 2024 20:28
MLenterman
changed the title
MLenterman
approved these changes
Jul 19, 2024
WeAreFrank-BOT
pushed a commit
that referenced
this pull request
Jul 19, 2024
## [1.20.1](v1.20.0...v1.20.1) (2024-07-19) ### 🔁 Continuous Integration * automatically bump the Frank!Framework version on a weekly basis ([#301](#301)) ([bad76bd](bad76bd))
|
🎉 This issue has been resolved in version 1.20.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
The F!F version in Zaakbrug occasianally needs to be updated manually when there is a new version of FrankFramework.
Now it is done automatically. Every Monday F!F will be checked if it has a new version. If there is no new version then we'll skip updating. In case there is a new F!F version then a new branch is created and the required changes in the files in zaakbrug repo are done and a new PR is created.
In case there is a change in the java file that zaakbrug uses as custom code (Parameter.java), then Parameter.java-orig file is also updated with the latest version of the Parameter.java file so that it is known that there is an update in Parameter.java file.