-
Notifications
You must be signed in to change notification settings - Fork 353
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
Update Semver to 7.5.4 and add licensing #1056
Merged
Merged
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
dsame
approved these changes
Jul 20, 2023
marko-zivic-93
approved these changes
Jul 20, 2023
IvanZosimov
approved these changes
Jul 20, 2023
marko-zivic-93
approved these changes
Jul 28, 2023
julioc-lopez
pushed a commit
to julioc-lopez/zk
that referenced
this pull request
Dec 8, 2023
Bumps actions/stale from 8 to 9. Release notes Sourced from actions/stale's releases. v9.0.0 Breaking Changes Action is now stateful: If the action ends because of operations-per-run then the next run will start from the first unprocessed issue skipping the issues processed during the previous run(s). The state is reset when all the issues are processed. This should be considered for scheduling workflow runs. Version 9 of this action updated the runtime to Node.js 20. All scripts are now run with Node.js 20 instead of Node.js 16 and are affected by any breaking changes between Node.js 16 and 20. What Else Changed Performance optimization that removes unnecessary API calls by @dsame #1033 fixes #792 Logs displaying current github API rate limit by @dsame #1032 addresses #1029 For more information, please read the action documentation and its section about statefulness New Contributors @jmeridth made their first contribution in actions/stale#984 @nikolai-laevskii made their first contribution in actions/stale#1020 @dusan-trickovic made their first contribution in actions/stale#1056 @aparnajyothi-y made their first contribution in actions/stale#1110 Full Changelog: actions/stale@v8...v9.0.0
julioc-lopez
pushed a commit
to julioc-lopez/zk
that referenced
this pull request
Dec 8, 2023
Bumps actions/stale from 8 to 9. Release notes Sourced from actions/stale's releases. v9.0.0 Breaking Changes Action is now stateful: If the action ends because of operations-per-run then the next run will start from the first unprocessed issue skipping the issues processed during the previous run(s). The state is reset when all the issues are processed. This should be considered for scheduling workflow runs. Version 9 of this action updated the runtime to Node.js 20. All scripts are now run with Node.js 20 instead of Node.js 16 and are affected by any breaking changes between Node.js 16 and 20. What Else Changed Performance optimization that removes unnecessary API calls by @dsame #1033 fixes #792 Logs displaying current github API rate limit by @dsame #1032 addresses #1029 For more information, please read the action documentation and its section about statefulness New Contributors @jmeridth made their first contribution in actions/stale#984 @nikolai-laevskii made their first contribution in actions/stale#1020 @dusan-trickovic made their first contribution in actions/stale#1056 @aparnajyothi-y made their first contribution in actions/stale#1110 Full Changelog: actions/stale@v8...v9.0.0
julioc-lopez
pushed a commit
to julioc-lopez/zk
that referenced
this pull request
Dec 8, 2023
Bumps actions/stale from 8 to 9. Release notes Sourced from actions/stale's releases. v9.0.0 Breaking Changes Action is now stateful: If the action ends because of operations-per-run then the next run will start from the first unprocessed issue skipping the issues processed during the previous run(s). The state is reset when all the issues are processed. This should be considered for scheduling workflow runs. Version 9 of this action updated the runtime to Node.js 20. All scripts are now run with Node.js 20 instead of Node.js 16 and are affected by any breaking changes between Node.js 16 and 20. What Else Changed Performance optimization that removes unnecessary API calls by @dsame #1033 fixes #792 Logs displaying current github API rate limit by @dsame #1032 addresses #1029 For more information, please read the action documentation and its section about statefulness New Contributors @jmeridth made their first contribution in actions/stale#984 @nikolai-laevskii made their first contribution in actions/stale#1020 @dusan-trickovic made their first contribution in actions/stale#1056 @aparnajyothi-y made their first contribution in actions/stale#1110 Full Changelog: actions/stale@v8...v9.0.0
kayman-mk
pushed a commit
to Hapag-Lloyd/Renovate-Global-Configuration
that referenced
this pull request
Dec 9, 2023
[![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [actions/stale](https://togithub.com/actions/stale) | action | major | `v8.0.0` -> `v9.0.0` | --- ### Release Notes <details> <summary>actions/stale (actions/stale)</summary> ### [`v9.0.0`](https://togithub.com/actions/stale/releases/tag/v9.0.0) [Compare Source](https://togithub.com/actions/stale/compare/v8.0.0...v9.0.0) #### Breaking changes 1. Action is now stateful: If the action ends because of [operations-per-run](https://togithub.com/actions/stale#operations-per-run) then the next run will start from the first unprocessed issue skipping the issues processed during the previous run(s). The state is reset when all the issues are processed. This should be considered for scheduling workflow runs. 2\. Version 9 of this action updated the runtime to Node.js 20. All scripts are now run with Node.js 20 instead of Node.js 16 and are affected by any breaking changes between Node.js 16 and 20. #### What else Changed 1. Performance optimization that removes unnecessary API calls by [@​dsame](https://togithub.com/dsame) [#​1033](https://togithub.com/actions/stale/pull/1033/) fixes [#​792](https://togithub.com/actions/stale/issues/792) 2. Logs displaying current github API rate limit by [@​dsame](https://togithub.com/dsame) [#​1032](https://togithub.com/actions/stale/pull/1032) addresses [#​1029](https://togithub.com/actions/stale/issues/1029) \ For more information, please read the [action documentation](https://togithub.com/actions/stale#readme) and its [section about statefulness](https://togithub.com/actions/stale#statefulness) #### New Contributors - [@​jmeridth](https://togithub.com/jmeridth) made their first contribution in [actions/stale#984 - [@​nikolai-laevskii](https://togithub.com/nikolai-laevskii) made their first contribution in [actions/stale#1020 - [@​dusan-trickovic](https://togithub.com/dusan-trickovic) made their first contribution in [actions/stale#1056 - [@​aparnajyothi-y](https://togithub.com/aparnajyothi-y) made their first contribution in [actions/stale#1110 **Full Changelog**: actions/stale@v8...v9.0.0 </details> --- ### 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 is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/Hapag-Lloyd/Renovate-Global-Configuration). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy44Ny4yIiwidXBkYXRlZEluVmVyIjoiMzcuODcuMiIsInRhcmdldEJyYW5jaCI6Im1haW4ifQ==--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
julioc-lopez
pushed a commit
to julioc-lopez/zk
that referenced
this pull request
Jan 9, 2024
Bumps actions/stale from 8 to 9. Release notes Sourced from actions/stale's releases. v9.0.0 Breaking Changes Action is now stateful: If the action ends because of operations-per-run then the next run will start from the first unprocessed issue skipping the issues processed during the previous run(s). The state is reset when all the issues are processed. This should be considered for scheduling workflow runs. Version 9 of this action updated the runtime to Node.js 20. All scripts are now run with Node.js 20 instead of Node.js 16 and are affected by any breaking changes between Node.js 16 and 20. What Else Changed Performance optimization that removes unnecessary API calls by @dsame #1033 fixes #792 Logs displaying current github API rate limit by @dsame #1032 addresses #1029 For more information, please read the action documentation and its section about statefulness New Contributors @jmeridth made their first contribution in actions/stale#984 @nikolai-laevskii made their first contribution in actions/stale#1020 @dusan-trickovic made their first contribution in actions/stale#1056 @aparnajyothi-y made their first contribution in actions/stale#1110 Full Changelog: actions/stale@v8...v9.0.0
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.
Description:
In the scope of this PR is a simple Semver version update (from
7.5.3
to7.5.4
). I mostly created this PR because I noticed after looking into #1011 thatpackage.json
still had an old version (7.3.5
) while the ones inpackage-lock
were bumped to7.5.1
. Potentially, due to the fact that the PR above is old, it created some merge conflicts, so doing it this way was probably more efficient.Unit tests were ran prior to committing and no errors were thrown.
Related issue:
Add link to the related issue.
Check list: