Skip to content

Releases: flex-development/grease

grease@1.1.0

26 Aug 23:51
grease@1.1.0
60b1c72
Compare
Choose a tag to compare

♻️ Code Improvements

  • node-typescript: update SemanticVersionUnstable definition (66538cb)
  • node-typescript: update SemanticVersionTag definition (549bf6d)
  • node: update grease options (1c4c898)

🔨 Build

  • node: install @flex-development/dtag@1.0.0 (17d4afd)

✨ Features

  • node: utils/getPrerelease (541a880)
  • node: autodetect prerelease (ea6c990)

🚚 Continuous Integration & Deployment

  • workflows: use yarn workspace command (79f0edf)

✏️ Housekeeping

  • node: update package keywords (8da62a3)
  • scripts: update build script (005e1c1)

grease@1.0.2

23 Aug 19:18
grease@1.0.2
Compare
Choose a tag to compare

📖 Documentation

  • node: update installation instructions (32699c2)
  • node: update package.json#homepage (6630524)

grease@1.0.1

18 Sep 16:08
grease@1.0.1
Compare
Choose a tag to compare

🐛 Fixes

  • node: CreateReleaseDTO#version failure when options.skip.tag is true (e8ede43)

grease@1.0.0 (🎂 First Release)

15 Aug 04:15
4a8195d
Compare
Choose a tag to compare

Overview

grease is a package release workflow tool for Node.js environments. Built on top of the standard-version library, it helps maintainers create releases and upload release assets via the GitHub CLI.

Release notes can be generated using the CHANGELOG entry for the most recent semver tag. Maintainers also have the option of generating blank notes, notes in birthday (first release) format, or skipping note generation entirely.

How It Works

  1. Follow the Conventional Commits Specification in your repository
  2. When ready to release, run grease(options: IGreaseOptions)

grease will then do the following:

  1. Retrieve the current package version by looking at packageFiles,
    falling back to the last git tag (if enabled)
  2. bump the version in bumpFiles based on your commits
  3. Generate a commit-based changelog (uses conventional-changelog under
    the hood)
  4. Create a new commit including bumpFiles and updated CHANGELOG
  5. Create a new tag with the new version number
  6. Check if the GitHub CLI is installed
  7. Generate release notes
  8. Create a new GitHub release