Updated ci.yml file and upgraded protocol version

[miantalha45]

Summary

Updated ci.yml file for changing the procedure of publishing on npm
upgraded protocol version in package.json

[Copilot]

Pull request overview

Updates the project’s npm publishing workflow and bumps the @metacall/protocol dependency version, aligning CI/release behavior with the new publishing approach.

Changes:

• Bump @metacall/protocol from ^0.1.24 to ^0.1.27 in package.json.
• Update GitHub Actions workflow permissions and change Node version used in CI.
• Change npm publishing approach (move away from the previous token-based npm-publish action configuration toward npm publish --provenance).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
package.json	Upgrades @metacall/protocol dependency version.
.github/workflows/ci.yml	Adjusts workflow permissions, Node version, and the npm publish step/procedure.

---

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

[Copilot]

This workflow step is invalid because it specifies both uses: and run: in the same step. GitHub Actions requires a step to use either an action (uses) or a shell command (run). Remove uses: JS-DevTools/npm-publish@v2 and keep the run block, or switch back to using the action with appropriate inputs (and no run).

Suggested change

uses: JS-DevTools/npm-publish@v2

[Copilot]

Since this is a scoped package (@metacall/deploy), npm publish commonly requires --access public (or publishConfig.access="public" in package.json) to avoid defaulting to restricted access. The previous workflow explicitly set access: 'public'; consider adding --access public (or publishConfig) back to prevent publish failures on tag builds.

Suggested change

	npm publish --provenance
	npm publish --access public --provenance

[Copilot]

package-lock.json is committed and still pins @metacall/protocol to the old range/version, so installs will continue using the locked version (or update the lock locally) despite this package.json bump. Please update and commit package-lock.json to reflect the new @metacall/protocol version so dependency resolution is deterministic and npm ci would remain consistent.

Suggested change

	"@metacall/protocol": "^0.1.27",
	"@metacall/protocol": "^0.1.26",