Release process to be automated

Open
#84 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
git, github-actions, typescript
Domain
ci-cd, devops, release

Research direction

No implementation files or tests are named. Start by reviewing the documented release sequence, including npm run all, the dist/ directory, versioning, tag updates, and GitHub release creation; done means this manual process is automated and produces the expected package, tags, and changelog.

Written by the indexing model from the issue text.

Description

👜 Totebag devops enhancement internal technical

  • Make sure your local main branch is up-to-date

    • git checkout main
    • git fetch upstream
    • git reset --hard upstream/main

  • Decide the version number of your next release, depending on the commits included:

    • a patch version X.X.(n+1) when the release includes only bug fixes or small new features
    • a minor version X.(n+1).0 when the release includes notable new features
    • a major version (n+1).0.0 when the release introduces breaking changes / major refactoring or changes

  • Package the action with npm run all

  • Git add the changes of the dist/ directory with git add -u

  • Bump the package version with npm version -f X.Y.Z with the version decided before

  • Publish to Github! git push --tags upstream main

  • Update the “Major” version sliding tag vN

    • git tag -d vN
    • git tag vN main
    • git push upstream vN --force

  • Create a new GitHub release with a comprehensive changelog on https://github.com/bump-sh/github-action/releases/new

Dominant language
TypeScript
Stars
47
Forks
11
Avg merge
3h 2m
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

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 bump-sh/github-action

All issues in bump-sh/github-action

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.