build-push-action icon indicating copy to clipboard operation
build-push-action copied to clipboard

chore(deps): Bump actions/checkout from 5 to 6

Open dependabot[bot] opened this issue 1 month ago • 0 comments

Bumps actions/checkout from 5 to 6.

Release notes

Sourced from actions/checkout's releases.

v6.0.0

What's Changed

Full Changelog: https://github.com/actions/checkout/compare/v5.0.0...v6.0.0

v6-beta

What's Changed

Updated persist-credentials to store the credentials under $RUNNER_TEMP instead of directly in the local git config.

This requires a minimum Actions Runner version of v2.329.0 to access the persisted credentials for Docker container action scenarios.

v5.0.1

What's Changed

Full Changelog: https://github.com/actions/checkout/compare/v5...v5.0.1

Changelog

Sourced from actions/checkout's changelog.

Changelog

V6.0.0

V5.0.1

V5.0.0

V4.3.1

V4.3.0

v4.2.2

v4.2.1

v4.2.0

v4.1.7

v4.1.6

v4.1.5

... (truncated)

Commits

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

dependabot[bot] avatar Nov 21 '25 11:11 dependabot[bot]

Do you see the bug in 3.x too? If so, the bug may not be related to Semantic command as that feature was not backported (due to the induced api change).

fcollonval avatar Jan 04 '23 13:01 fcollonval

I see it on both 3.5 and master. Maybe was introduced by #10469? But then I don't know why it is also seen on 4.0.

krassowski avatar Jan 04 '23 13:01 krassowski

I can also repro with master

JasonWeill avatar Jan 05 '23 18:01 JasonWeill

Looking into this, actually this concerns all commands that do not have an existing shortcuts. The shortcut editors does not get the list of commands but the shortcuts settings.

Fun fact the list of all commands is built to set the description of the JSON schema that is displayed in the JSON Settings editor.

fcollonval avatar Feb 15 '23 16:02 fcollonval

Adding the list of commands without shortcuts is easy. But the trouble is that they don't have selectors. So the UI must be extended to allow for a selector to be defined; may be we could define a default selector (function of the command category (?)).

fcollonval avatar Feb 15 '23 17:02 fcollonval

Looking into this, actually this concerns all commands that do not have an existing shortcuts

Thanks for looking into it futher!

may be we could define a default selector (function of the command category (?)

or just go with "body" and advise users to change it as needed?

krassowski avatar Feb 15 '23 20:02 krassowski

Per discussion at triage, this affects all commands that don't yet have shortcuts, not just semantic commands.

JasonWeill avatar Nov 05 '24 17:11 JasonWeill

We can think of several ways to set a new shortcut to a command (without default):

  • display all the commands in the list (if requested only), allow creating a shortcut on any of them and allow setting the associated selector/args for the command. This is the current state of https://github.com/jupyterlab/jupyterlab/pull/18163
  • add a button to add a command, which could (1) open a form to set the command name, the selector and the args, or (2) set the command name on an empty row, and the selector/args in a form. This is more or less what is suggested in https://github.com/jupyterlab/jupyterlab/pull/18163#issuecomment-3613266743 by @krassowski, IIUC

If someone has an opinion on it.

brichet avatar Dec 05 '25 07:12 brichet