chore(deps): update dependency org.apache.felix:maven-bundle-plugin to v5.1.9#431
chore(deps): update dependency org.apache.felix:maven-bundle-plugin to v5.1.9#431renovate[bot] wants to merge 12 commits intomainfrom
Conversation
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 **
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
|
This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
|
This PR was closed because it has been stalled with no activity. |
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update ( If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
This PR contains the following updates:
5.1.8→5.1.9Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
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.