Release a v1.0.0

Open
#38 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, javascript, node.js
Domain
ci-cd, devops, release

Research direction

Review the issue discussion and the linked action/pull request #39 first, then inspect the repository's @main references and current package versioning. Confirm the v1.0.0 release plan, the v1 major tag, npm versioning, and automatic tag movement are all agreed and documented before considering the work done.

Written by the indexing model from the issue text.

Description

If there's no objections, I'm going to tag a v1.0.0 next week?

I'll also move a v1 tag there and update all the @main references to @v1.

I intend to just use npm version for the time being to bump versions, and a small workflow to automatically move the major tag forward whenever there's a new tag on HEAD (main).

Dominant language
JavaScript
Stars
12
Forks
3
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 pkgjs/action

All issues in pkgjs/action

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.