Version increment/deploy path

Open
#276 12 comments 1 reaction 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, javascript, node.js
Domain
cli, devops, release

Research direction

Start by reviewing CHANGELOG.md, package.json, and test/main.js#L65 to understand the version values that must stay aligned. Compare the proposed Travis and Git hook paths, then define a release flow that increments and tags the latest version on changes to master and updates all three locations.

Written by the indexing model from the issue text.

Description

enhancement help wanted

Thinking about, and open for suggestions, a release management that can automatically increment and tag latest version on changes to master.

Needs to update:

  • CHANGELOG.md
  • test/main.js#L65
  • package.json version

Travis? Git hooks?

Dominant language
JavaScript
Stars
1.4k
Forks
185
No merged PRs in 30d

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 motdotla/node-lambda

All issues in motdotla/node-lambda

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.