Enable immutable releases via automated version tag management

[Copilot]

Closes: #[issue_number]

Implements automated release versioning to enable immutable version references. When a release is published, creates both specific semantic version tags (v1.0.0) and updates major version tags (v1) automatically.

Changes

• .github/workflows/publish.yml: Workflow using git commands to manage version tags on release publish events. Extracts major version from semver tags and automatically creates/updates major version tags to point to the latest release. Includes contents: write permission for tag creation.
• README.md: Documents versioning options with examples:
  • @v1.0.0 - immutable specific version
  • @v1 - latest within major version (recommended)
  • @main - development branch (not recommended for production)

The implementation uses a production-ready, git-based approach that is widely adopted by popular GitHub Actions, ensuring reliability and maintainability.

Users can now pin to stable versions instead of tracking @main.

Original prompt

enable immutable releases for this action

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[thst-nordic]

@copilot publich-action has this warning.

Please note: this action is for internal usage only, issues are disabled and contributing PRs will not be reviewed. We also do not recommend this action for public or production usage while it is still in development.

This action adds reliability to the new action versions publishing and handles the following cases:

Update a major tag (v1, for example) to point to the latest release (v1.2.1, for example).
Create a major tag from the latest released tag if a major tag doesn't exist

is there a better option?

[Copilot]

@copilot publich-action has this warning.

Please note: this action is for internal usage only, issues are disabled and contributing PRs will not be reviewed. We also do not recommend this action fo...

You're right - I've replaced it with a standard git-based approach that's production-ready and widely used by popular GitHub Actions. The new workflow (commit 5f369de) uses git commands directly to create and update major version tags when releases are published. This eliminates the dependency on the internal-only action while providing the same functionality.