Screeps/screeps-deploy-action
4
1
Fork 0
Code Issues 1 Pull Requests 3 Actions Packages Releases Activity

fix(deps): update dependency @actions/core to v3 #69

Open
Renovate wants to merge 1 commits from renovate/actions-core-3.x into main
pull from: renovate/actions-core-3.x
merge into: Screeps:main
Conversation 2 Commits 1 Files Changed 2 +17 -17
Renovate commented 2026-02-08 18:08:25 +01:00
Member
Copy Link

This PR contains the following updates:

Package Change Age Confidence
@actions/core (source) ^2.0.0 → ^3.0.0 age confidence

Release Notes

actions/toolkit (@​actions/core)

v3.0.0

  • Breaking change: Package is now ESM-only
    • CommonJS consumers must use dynamic import() instead of require()

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.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [@actions/core](https://github.com/actions/toolkit/tree/main/packages/core) ([source](https://github.com/actions/toolkit/tree/HEAD/packages/core)) | [`^2.0.0` → `^3.0.0`](https://renovatebot.com/diffs/npm/@actions%2fcore/2.0.3/3.0.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@actions%2fcore/3.0.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@actions%2fcore/2.0.3/3.0.0?slim=true) | --- ### Release Notes <details> <summary>actions/toolkit (@&#8203;actions/core)</summary> ### [`v3.0.0`](https://github.com/actions/toolkit/blob/HEAD/packages/core/RELEASES.md#300) - **Breaking change**: Package is now ESM-only - CommonJS consumers must use dynamic `import()` instead of `require()` </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 becomes conflicted, 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 [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0Mi45NC4wIiwidXBkYXRlZEluVmVyIjoiNDIuOTQuMCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiQXV0b21hdGlvbiJdfQ==-->
Renovate added 1 commit 2026-02-08 18:08:25 +01:00
fix(deps): update dependency @actions/core to v3
Some checks failed
renovate/artifacts Artifact file update failure
Lint / pre-commit Linting (push) Successful in 1m11s
Details
Test / Run Tests (push) Failing after 1m9s
Details
7577dcc9ad
Renovate commented 2026-02-08 18:08:29 +01:00
Author
Member
Copy Link

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package.json
Command failed: /bin/sh -c npm run build
Error: Module not found: Error: Package path . is not exported from package /tmp/renovate/repos/gitea/Screeps/screeps-deploy-action/node_modules/@actions/core (see exports field in /tmp/renovate/repos/gitea/Screeps/screeps-deploy-action/node_modules/@actions/core/package.json)
Did you mean './@actions/core'?
Requests that should resolve in the current directory need to start with './'.
Requests that start with a name are treated as module requests and resolve within module directories (node_modules).
If changing the source code is not an option there is also a resolve options called 'preferRelative' which tries to resolve these kind of requests in the current directory too.
    at /tmp/renovate/repos/gitea/Screeps/screeps-deploy-action/node_modules/@vercel/ncc/dist/ncc/index.js.cache.js:23:2001849
    at /tmp/renovate/repos/gitea/Screeps/screeps-deploy-action/node_modules/@vercel/ncc/dist/ncc/index.js.cache.js:23:389111
    at _done (eval at create (/tmp/renovate/repos/gitea/Screeps/screeps-deploy-action/node_modules/@vercel/ncc/dist/ncc/index.js.cache.js:21:81694), <anonymous>:9:1)
    at eval (eval at create (/tmp/renovate/repos/gitea/Screeps/screeps-deploy-action/node_modules/@vercel/ncc/dist/ncc/index.js.cache.js:21:81694), <anonymous>:34:22)
### ⚠️ Artifact update problem Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens: - any of the package files in this branch needs updating, or - the branch becomes conflicted, or - you click the rebase/retry checkbox if found above, or - you rename this PR's title to start with "rebase!" to trigger it manually The artifact failure details are included below: ##### File name: package.json ``` Command failed: /bin/sh -c npm run build Error: Module not found: Error: Package path . is not exported from package /tmp/renovate/repos/gitea/Screeps/screeps-deploy-action/node_modules/@actions/core (see exports field in /tmp/renovate/repos/gitea/Screeps/screeps-deploy-action/node_modules/@actions/core/package.json) Did you mean './@actions/core'? Requests that should resolve in the current directory need to start with './'. Requests that start with a name are treated as module requests and resolve within module directories (node_modules). If changing the source code is not an option there is also a resolve options called 'preferRelative' which tries to resolve these kind of requests in the current directory too. at /tmp/renovate/repos/gitea/Screeps/screeps-deploy-action/node_modules/@vercel/ncc/dist/ncc/index.js.cache.js:23:2001849 at /tmp/renovate/repos/gitea/Screeps/screeps-deploy-action/node_modules/@vercel/ncc/dist/ncc/index.js.cache.js:23:389111 at _done (eval at create (/tmp/renovate/repos/gitea/Screeps/screeps-deploy-action/node_modules/@vercel/ncc/dist/ncc/index.js.cache.js:21:81694), <anonymous>:9:1) at eval (eval at create (/tmp/renovate/repos/gitea/Screeps/screeps-deploy-action/node_modules/@vercel/ncc/dist/ncc/index.js.cache.js:21:81694), <anonymous>:34:22) ```
AutoReview changed title from fix(deps): update dependency @actions/core to v3 to Update @actions/core dependency to v3 2026-02-08 18:08:55 +01:00
AutoReview commented 2026-02-08 18:09:15 +01:00
Member
Copy Link

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ Recommended focus areas for review

Breaking Changes

Bumping @actions/core to v3 may introduce breaking API changes; verify that all core function calls and inputs are still supported and update code if needed.

 
"@actions/core": "^3.0.0",
Lockfile Update

Ensure the corresponding lockfile (package-lock.json or yarn.lock) is updated to reflect the new version of @actions/core and committed in this PR.

 
"@actions/core": "^3.0.0",
## PR Reviewer Guide 🔍 Here are some key observations to aid the review process: <table> <tr><td>⏱️&nbsp;<strong>Estimated effort to review</strong>: 1 🔵⚪⚪⚪⚪</td></tr> <tr><td>🧪&nbsp;<strong>No relevant tests</strong></td></tr> <tr><td>🔒&nbsp;<strong>No security concerns identified</strong></td></tr> <tr><td>⚡&nbsp;<strong>Recommended focus areas for review</strong><br><br> <details><summary><a href='https://git.horstenkamp.eu/Screeps/screeps-deploy-action/src/branch/renovate/actions-core-3.x/package.json#L12-L12'><strong>Breaking Changes</strong></a> Bumping @actions/core to v3 may introduce breaking API changes; verify that all core function calls and inputs are still supported and update code if needed. </summary> ```json "@actions/core": "^3.0.0", ``` </details> <details><summary><a href='https://git.horstenkamp.eu/Screeps/screeps-deploy-action/src/branch/renovate/actions-core-3.x/package.json#L12-L12'><strong>Lockfile Update</strong></a> Ensure the corresponding lockfile (package-lock.json or yarn.lock) is updated to reflect the new version of @actions/core and committed in this PR. </summary> ```json "@actions/core": "^3.0.0", ``` </details> </td></tr> </table>
Renovate changed title from Update @actions/core dependency to v3 to fix(deps): update dependency @actions/core to v3 2026-02-08 18:20:50 +01:00
Some checks failed
renovate/artifacts Artifact file update failure
Lint / pre-commit Linting (push) Successful in 1m11s
Required
Details
Test / Run Tests (push) Failing after 1m9s
Required
Details
Some required checks were not successful.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/actions-core-3.x:renovate/actions-core-3.x
git checkout renovate/actions-core-3.x
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something is not working
 chore
duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
AutoReview Philipp Renovate runner
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Screeps/screeps-deploy-action#69
Delete Branch "renovate/actions-core-3.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?