Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Feature: Add Workflow for Manual Version Bump

Open
#507 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions
Domain
ci-cd, release

Research direction

Start by reviewing the repository's GitHub Actions workflow configuration and the Universal Version Bump action documentation. Add a manually triggerable workflow with patch, minor, and major choices, then verify that a run updates the project version and appears in the Actions tab.

Written by the indexing model from the issue text.

Description

enhancement

We should add a GitHub Actions workflow powered by Universal Version Bump.
This will allow maintainers to manually trigger version bumps from the Actions tab, keeping the project version consistent and reducing manual errors.

✅ Acceptance Criteria

  • A workflow is visible in the Actions tab.
  • You can choose the bump type (patch, minor, major).
  • Running the workflow updates the version automatically using Universal Version Bump.
  • (Optional) Extend the workflow later to include Git tagging + release creation.

🌟 Why This Matters

  • Keeps project versions aligned with development progress.
  • Reduces manual overhead and error-prone version edits.
  • Leverages Universal Version Bump for reliable and consistent updates.
  • Lays foundation for future enhancements like automated tagging, changelog updates, and releases.

🙋 If you’d like, I can open a PR to add this workflow.

Dominant language
TypeScript
Stars
661
Forks
214
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/vscode-github-actions

All issues in github/vscode-github-actions

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.