chore(deps): bump marked and semantic-release #385
Closed
Conversation
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
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
the
dependencies
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/marked-and-semantic-release-4.2.12
branch
2 times, most recently
from
761a7a1 to
cb38fb2
Compare
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/marked-and-semantic-release-4.2.12
branch
3 times, most recently
from
7fe99e3 to
652ea45
Compare
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/marked-and-semantic-release-4.2.12
branch
2 times, most recently
from
b12e340 to
cf6a237
Compare
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/marked-and-semantic-release-4.2.12
branch
2 times, most recently
from
9f7b394 to
99c116e
Compare
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/marked-and-semantic-release-4.2.12
branch
2 times, most recently
from
478951d to
e62a2b5
Compare
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/marked-and-semantic-release-4.2.12
branch
2 times, most recently
from
8c3f1ef to
2e15123
Compare
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/marked-and-semantic-release-4.2.12
branch
2 times, most recently
from
600198b to
7e36358
Compare
Bumps [marked](https://github.com/markedjs/marked) to 4.2.12 and updates ancestor dependency [semantic-release](https://github.com/semantic-release/semantic-release). These dependencies need to be updated together. Updates `marked` from 2.1.3 to 4.2.12 - [Release notes](https://github.com/markedjs/marked/releases) - [Changelog](https://github.com/markedjs/marked/blob/master/.releaserc.json) - [Commits](markedjs/marked@v2.1.3...v4.2.12) Updates `semantic-release` from 18.0.1 to 20.0.2 - [Release notes](https://github.com/semantic-release/semantic-release/releases) - [Commits](semantic-release/semantic-release@v18.0.1...v20.0.2) --- updated-dependencies: - dependency-name: marked dependency-type: indirect - dependency-name: semantic-release dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/marked-and-semantic-release-4.2.12
branch
from
7e36358 to
702fcf6
Compare
|
Superseded by #408. |
dependabot
bot
deleted the
dependabot/npm_and_yarn/marked-and-semantic-release-4.2.12
branch
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.
Bumps marked to 4.2.12 and updates ancestor dependency semantic-release. These dependencies need to be updated together.
Updates
markedfrom 2.1.3 to 4.2.12Release notes
Sourced from marked's releases.
... (truncated)
Commits
137d3b4chore(release): 4.2.12 [skip ci]0f0de55🗜️ build v4.2.12 [skip ci]4704e19chore: add build version to build commitd2ab474fix: readd build script in ci3c140c6chore(release): 4.2.11 [skip ci]22ac2cffix: just build in versionfd759b3fix: use version5367a77chore(release): 4.2.9 [skip ci]96380c3fix: fix version5ca781echore(release): 4.2.8 [skip ci]Updates
semantic-releasefrom 18.0.1 to 20.0.2Release notes
Sourced from semantic-release's releases.
... (truncated)
Commits
cb45d27fix(deps): update dependency semver-diff to v4 (#1915)f914c1efix(deps): update dependency cosmiconfig to v8c4da008fix(deps): update dependency hosted-git-info to v6b707475chore(deps): update dependency sinon to v15 (#2653)b957934chore(deps): update dependency fs-extra to v11 (#2650)4b74f00chore(deps): update dependency ava to v5 (#2649)bbb5e5achore(deps): update dependency testdouble to v3.16.8 (#2646)a1e0467chore(deps): update dependency sinon to v14.0.2 (#2645)b9b5c76Merge pull request #2607 from semantic-release/beta91bcb6bMerge branch 'master' of github.com:semantic-release/semantic-release into betaDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.