chore(deps): bump marked and gulp-markdown - #312
Merged
Conversation
Bumps [marked](https://github.com/markedjs/marked) to 9.1.6 and updates ancestor dependency [gulp-markdown](https://github.com/sindresorhus/gulp-markdown). These dependencies need to be updated together. Updates `marked` from 0.3.19 to 9.1.6 - [Release notes](https://github.com/markedjs/marked/releases) - [Changelog](https://github.com/markedjs/marked/blob/master/.releaserc.json) - [Commits](markedjs/marked@v0.3.19...v9.1.6) Updates `gulp-markdown` from 2.0.1 to 8.0.0 - [Release notes](https://github.com/sindresorhus/gulp-markdown/releases) - [Commits](sindresorhus/gulp-markdown@v2.0.1...v8.0.0) --- updated-dependencies: - dependency-name: marked dependency-version: 9.1.6 dependency-type: indirect - dependency-name: gulp-markdown dependency-version: 8.0.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
kt3k
added a commit
that referenced
this pull request
Aug 12, 2026
* ci: migrate from CircleCI to GitHub Actions CircleCI has been unable to check out the repository since its checkout key stopped working, so nothing has been deployed since 2023-10. Replace it with GitHub Actions and publish through the Pages deployment API instead of committing the build output to the master branch. - add .github/workflows/deploy.yml (build on every push/PR, deploy to Pages on source) - drop .circleci/config.yml and update.sh - drop rimraf and status-back, only used by the two files above - bump .node-version from 8.1.4 to 24, the current LTS - fix bulbofile.js for the ESM majors of gulp-nunjucks and gulp-markdown pulled in by #312 and #313, which broke the build - emit CNAME into build/ so the custom domain survives in the artifact * ci: publish to master instead of GitHub Pages nodejs.jp turns out to be served by Netlify out of the master branch, not by GitHub Pages, so deploying through the Pages API would not touch the live site. Replace the Pages deploy job with one that builds into a checkout of master and pushes, which is what update.sh did under CircleCI.
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
1 participant
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 9.1.6 and updates ancestor dependency gulp-markdown. These dependencies need to be updated together.
Updates
markedfrom 0.3.19 to 9.1.6Release notes
Sourced from marked's releases.
... (truncated)
Commits
86e0eb5chore(release): 9.1.6 [skip ci]f9d08ccfix: fix instance options sent to lexer and parser (#3073)daa24eechore(deps-dev): Bump@arethetypeswrong/clifrom 0.12.2 to 0.13.1 (#3080)1a66565chore(deps-dev): Bump@typescript-eslint/eslint-pluginfrom 6.9.0 to 6.9.1 (#...b1eb392chore(deps-dev): Bump@semantic-release/release-notes-generatorfrom 12.0.0 t...5ca0f6cchore(deps-dev): Bump rollup from 4.1.5 to 4.3.0 (#3082)41195c9chore(deps-dev): Bump@semantic-release/commit-analyzerfrom 11.0.0 to 11.1.0...dfa6d30chore(deps-dev): Bump@typescript-eslint/parserfrom 6.9.0 to 6.9.1 (#3079)915f51dchore(deps-dev): Bump@semantic-release/npmfrom 11.0.0 to 11.0.1 (#3078)ae084b1chore(deps-dev): Bump semantic-release from 22.0.5 to 22.0.7 (#3077)Maintainer changes
This version was pushed to npm by tonybrix, a new releaser for marked since your current version.
Updates
gulp-markdownfrom 2.0.1 to 8.0.0Release notes
Sourced from gulp-markdown's releases.
Commits
cf5f07c8.0.0e9388daRequire Node.js 1862e151e7.0.07fa7452Require Node.js 14 and move to ESM3ca7befFix CI80fa0b86.0.08bebd63Require Node.js 10 and upgrade tomarked2a700f48Move to GitHub Actions (#19)16ba8935.1.0c58aa89Allow customization of themarkedrenderer (#18)Dependabot 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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@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.