Bump marked from 1.2.8 to 1.2.9 #27228
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
|
@dependabot rebase |
|
@dependabot recreate |
|
The bot is somehow stuck on this one. I'll rebase manually. |
MichaIng
force-pushed
the
dependabot/npm_and_yarn/stable21/marked-1.2.9
branch
from
9e9dedc to
b3ad424
Compare
|
/compile amend / |
npmbuildbot-nextcloud
bot
force-pushed
the
dependabot/npm_and_yarn/stable21/marked-1.2.9
branch
from
b3ad424 to
5b06ae1
Compare
MichaIng
force-pushed
the
dependabot/npm_and_yarn/stable21/marked-1.2.9
branch
from
5b06ae1 to
18d001e
Compare
github-actions
bot
force-pushed
the
dependabot/npm_and_yarn/stable21/marked-1.2.9
branch
from
18d001e to
dbc195b
Compare
|
/rebase EDIT: Okay this github-actions bot rebase doesn't seem to trigger the tests 🤔. |
github-actions
bot
force-pushed
the
dependabot/npm_and_yarn/stable21/marked-1.2.9
branch
from
dbc195b to
a77e4e7
Compare
MichaIng
force-pushed
the
dependabot/npm_and_yarn/stable21/marked-1.2.9
branch
from
a77e4e7 to
c43ab5d
Compare
Yes, that's a github limitation :) |
|
Good to know. And my manual rebase triggers everything, but not the drone. Can it be triggered manually for this branch? The compile bot is down, so that one cannot be used. Probably it's okay to merge as is, but at least I'm not brave enough to approve as long as not all check have passed 🙂. |
back up |
|
/compile amend / |
|
Drone is having issues accepting those old dependabot PRs |
|
Hmm, and dependabot does not react to Wait, I think I know now why the bot has issues here: https://github.com/nextcloud/server/pulls?q=Bump+marked+from+1.2.8 The previews dependabot PRs were closed (aside of the one against master), which actually bumped marked to 2.0.0 already: https://github.com/nextcloud/server/pulls?q=Bump+marked+from+1.2.8 A little prove on my guess at the vue bump PR, that (non-preview) dependabot does not reopen or handle dependencies further when preview dependabot PRs were closed (contradicting the info it edited into the PRs OP). See #26414 which was closed in April already, so it's definitely not that we only need to wait for another workflow run. So I suggest to reopen #26414, rebase it manually and compile + amend scripts. There are already newer versions in the meantime, but after merging that PR, I guess non-preview dependabot will again track new releases. Or probably it's easier, when possible, to reset the dependabot's memory? |
|
I think it would be best to have this in before |
Bumps [marked](https://github.com/markedjs/marked) from 1.2.8 to 1.2.9. - [Release notes](https://github.com/markedjs/marked/releases) - [Changelog](https://github.com/markedjs/marked/blob/master/release.config.js) - [Commits](markedjs/marked@v1.2.8...v1.2.9) Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: npmbuildbot-nextcloud[bot] <npmbuildbot-nextcloud[bot]@users.noreply.github.com>
MichaIng
force-pushed
the
dependabot/npm_and_yarn/stable21/marked-1.2.9
branch
from
c43ab5d to
b8be9c6
Compare
I didn't realized this was stable21 |
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Bumps marked from 1.2.8 to 1.2.9.
Release notes
Sourced from marked's releases.
Commits
f2535f1chore(release): 1.2.9 [skip ci]f0dc8a2🗜️ build [skip ci]1e36afdfix: allow sublist to be single space in pedantic (#1924)b97b802chore(deps-dev): Bump rollup from 2.38.0 to 2.38.3 (#1922)409ef11chore(deps-dev): Bump@rollup/plugin-babelfrom 5.2.2 to 5.2.3 (#1917)f86549dchore(deps-dev): Bump rollup from 2.38.0 to 2.38.2 (#1916)b2fe7c1chore(deps-dev): Bump uglify-js from 3.12.5 to 3.12.6 (#1919)aec6b9dchore(deps-dev): Bump@rollup/plugin-commonjsfrom 17.0.0 to 17.1.0 (#1918)afb285dchore(deps-dev): Bump eslint from 7.18.0 to 7.19.0 (#1920)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 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)