Release 0.8.2#1624
Merged
UziTech merged 3 commits intomarkedjs:masterfrom Mar 22, 2020
UziTech:release-0.8.2
Merged
Conversation
|
This pull request is being automatically deployed with ZEIT Now (learn more). 🔍 Inspect: https://zeit.co/markedjs/markedjs/5z6k4mrtb |
styfle
approved these changes
Mar 22, 2020
| "devDependencies": { | ||
| "@babel/core": "^7.7.5", | ||
| "@babel/preset-env": "^7.7.6", | ||
| "@babel/core": "^7.9.0", |
Member
There was a problem hiding this comment.
I would prefer these dependency bumps in a separate PR.
zhenalexfan
pushed a commit
to zhenalexfan/MarkdownHan
that referenced
this pull request
Nov 8, 2021
Release 0.8.2
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We should create another release to fix #1621. I feel like quite a few people might run into that bug.
I also updated the devdependencies.
Release Notes
Fixes
Docs
Publisher
$ npm versionhas been run.masterwith correct version number.$ npm publishhas been run.Note: If merges to
masteroccur after submitting this PR and before running$ npm pubishyou should be able toupstream/master(git pull upstream master) into the branch holding this version,$ npm run buildto regenerate theminfile, andCommitter
In most cases, this should be someone different than the publisher.
package.jsonhas been updated (see PUBLISHING.md).marked.min.jshas been updated.