forked from dotCMS/core
-
Notifications
You must be signed in to change notification settings - Fork 2
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
chore(deps): update dependency biz.aqute.bnd:biz.aqute.bndlib to v7 - abandoned #349
Open
renovate
wants to merge
12
commits into
main
Choose a base branch
from
renovate/biz.aqute.bnd-biz.aqute.bndlib-7.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
codeowners with workflow devs ### Proposed Changes * change 1 * change 2 ### Checklist - [ ] Tests - [ ] Translations - [ ] Security Implications Contemplated (add notes if applicable) ### Additional Info ** any additional useful context or info ** ### Screenshots Original | Updated :-------------------------:|:-------------------------: ** original screenshot ** | ** updated screenshot **
This pull request includes several changes to the deployment process for the JavaScript SDK in the `.github/actions/core-cicd/deployment/deploy-javascript-sdk/action.yml` file. The primary focus is on updating the versioning and tagging system from "alpha" to "beta". Changes to versioning and tagging: * Updated the example projects to point to the 'next' tag instead of 'latest' to prevent version inconsistency. * Changed the default `npm-package-tag` from 'alpha' to 'beta'. * Modified the script to fetch the current version using the 'beta' tag instead of 'alpha', and set the initial version to "0.0.1-beta.0" if no current version is found. * Adjusted the version calculation logic to increment the beta version number instead of the alpha number. * Changed the npm dist-tag addition command to use the 'next' tag instead of 'latest'.
Just a file to trigger the workflow
This pull request includes a small but important change to the deployment script for the JavaScript SDK. The modification ensures that the `CURRENT_VERSION` is correctly set even if the retrieved version is `null`. * [`.github/actions/core-cicd/deployment/deploy-javascript-sdk/action.yml`](diffhunk://#diff-b47e2bc3507c79547b7f53206919f60585f49479fa09c01ee9ab15eb6bb4c068L74-R74): Updated the condition to check if `CURRENT_VERSION` is `null` and set it to `0.0.1-beta.0` if true.
Just trigger the workflow
### Proposed Changes * change 1 * change 2 ### Checklist - [ ] Tests - [ ] Translations - [ ] Security Implications Contemplated (add notes if applicable) ### Additional Info ** any additional useful context or info ** ### Screenshots Original | Updated :-------------------------:|:-------------------------: ** original screenshot ** | ** updated screenshot **
### Proposed Changes * change 1 * change 2 ### Checklist - [ ] Tests - [ ] Translations - [ ] Security Implications Contemplated (add notes if applicable) ### Additional Info ** any additional useful context or info ** ### Screenshots Original | Updated :-------------------------:|:-------------------------: ** original screenshot ** | ** updated screenshot **
Autoclosing SkippedThis PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error. |
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.
This PR contains the following updates:
6.4.0
->7.1.0
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
bndtools/bnd (biz.aQute.bnd:biz.aQute.bndlib)
v7.1.0
: Bnd/Bndtools 7.1.0Compare Source
See Release Notes.
v7.0.0
: Bnd/Bndtools 7.0.0Compare Source
This is the first release on Java 17.
See Release Notes.
v6.4.1
: Classic Bndtools/bnd 6.4.1 (only runtime bundles, no plugins)Compare Source
This is not a full release! It is maintained as a line for security and important fixes of the runtime bundles on Java 1.8.
See https://github.com/bndtools/bnd/wiki/Changes-in-6.4.1-classic
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.