Update dependency @actions/core to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@actions/core (source)	1.11.1 -> 2.0.0

---

Release Notes

actions/toolkit (@​actions/core)

v2.0.0

• Add support for Node 24 #​2110
• Bump @​actions/http-client from 2.0.1 to 3.0.0

---

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 was generated by Mend Renovate. View the repository job log.

[renovate]

Edited/Blocked Notification

Renovate 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.

⚠️ Warning: custom changes will be lost.

[mPickert]

after running nmp ci and pushing it still failed with some missing modules
i tried adding the missing modules which still didnt fix it
maybe someone else can take a look at it otherwise ill do it next week

[maltinabasse]

Update on Project Setup

We have removed the node_modules directory and added the @vercel/ncc dependency to build the bundle.
The bundled script is now placed into the dist folder. This file is generated from the root index.js file.

After you run:

npm ci
npm run build

The file in the dist folder will be updated automatically. This bundled file must also be checked in to the repository, as it is the entry point for the GitHub Action.

See GitHub Docs: Commit, tag, and push your action.

Current Status

The project is now configured according to the official documentation.

@wawe

Could you please check the new project structure and verify if this should work for us?
Unfortunately, we don’t know why the node_modules were checked in earlier.
Maybe you can help?

[wawe]

node_modules was checked in because the dependencies have to be included, as the documentation says.