Skip to content

Release 0.6.1 - #1421

Merged
UziTech merged 1 commit into
markedjs:masterfrom
UziTech:release-0.6.1
Feb 19, 2019
Merged

Release 0.6.1#1421
UziTech merged 1 commit into
markedjs:masterfrom
UziTech:release-0.6.1

Conversation

@UziTech

@UziTechUziTech commented Feb 18, 2019

Copy link
Copy Markdown
Member

Publisher

  • $ npm version has been run.
  • Release notes in draft GitHub release are up to date
  • Release notes include which flavors and versions of Markdown are supported by this release
  • Committer checklist is complete.
  • Merge PR.
  • Publish GitHub release using master with correct version number.
  • $ npm publish has been run.
  • Create draft GitHub release to prepare next release.

Note: If merges to master occur after submitting this PR and before running $ npm pubish you should be able to

  1. pull from upstream/master (git pull upstream master) into the branch holding this version,
  2. run $ npm run build to regenerate the min file, and
  3. commit and push the updated changes.

Committer

In most cases, this should be someone different than the publisher.

  • Version in package.json has been updated (see PUBLISHING.md).
  • The marked.min.js has been updated; or,
  • release does not change library.
  • CI is green (no forced merge required).

Release Notes

Fixes

Docs

@styflestyfle left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@UziTech
UziTech merged commit c679e5e into markedjs:masterFeb 19, 2019
@UziTech

Copy link
Copy Markdown
MemberAuthor

v0.6.1 has been released 🚢 🎉

@UziTech
UziTech deleted the release-0.6.1 branch February 19, 2019 20:12
zhenalexfan pushed a commit to zhenalexfan/MarkdownHan that referenced this pull request Nov 8, 2021
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@UziTech@styfle@joshbruce