Updated publish workflow

[PreciousOritsedere]

Fixes applied

• Removed token authentication: ${{ secrets.NPM_TOKEN }} from the publish steps.

• Added OIDC permissions: id-token: write at the workflow and job levels.

• Updated npm version: Added npm install -g npm@latest to ensure npm >= 11.5.1 (required for OIDC).

• Switched to direct npm publish: Replaced JS-DevTools/npm-publish with direct npm publish commands so npm uses the OIDC token from setup-node.

• Fixed repository URL case: Updated package.json repository URL from git+https://github.com/solidos/solid-ui.git to git+https://github.com/SolidOS/solid-ui.git to match the GitHub repository name.

[Copilot]

Pull request overview

This PR standardizes Node.js version specifications and updates the npm publish workflow configuration.

Changes:

• Standardized Node.js version format from string notation (e.g., '20.x') to numeric notation (e.g., 20)
• Added Node.js 24 to the test matrix
• Removed explicit NPM_TOKEN configuration from publish steps

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[PreciousOritsedere]

@jeswr this has been on auto merge since yesterday

[jeswr]

@PreciousOritsedere

You've changed the names of the build jobs by making the node variables 22 rather than 22.x. This means you'll need to update the names of the required job in the branch protections for this repo for this branch to merge.

[PreciousOritsedere]

@PreciousOritsedere

You've changed the names of the build jobs by making the node variables 22 rather than 22.x. This means you'll need to update the names of the required job in the branch protections for this repo for this branch to merge.

@jeswr I checked the settings, and I did not see any existing branch protections

[bourgeoa]

@PreciousOritsedere
Settings/Rules/Rulesets/General Ruleset is active
Look at item Require status checks to pass
select Show Additional Settings

I removed not existing ones and added the new ones