Skip to content

MAINT: Bump actions/setup-node from 3.6.0 to 3.7.0#24124

Merged
charris merged 1 commit intomainfrom
dependabot/github_actions/actions/setup-node-3.7.0
Jul 5, 2023
Merged

MAINT: Bump actions/setup-node from 3.6.0 to 3.7.0#24124
charris merged 1 commit intomainfrom
dependabot/github_actions/actions/setup-node-3.7.0

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 5, 2023

Bumps actions/setup-node from 3.6.0 to 3.7.0.

Release notes

Sourced from actions/setup-node's releases.

v3.7.0

What's Changed

In scope of this release we added a logic to save an additional cache path for yarn 3 (related pull request and feature request). Moreover, we added functionality to use all the sub directories derived from cache-dependency-path input and add detect all dependencies directories to cache (related pull request and feature request).

Besides, we made such changes as:

New Contributors

Full Changelog: actions/setup-node@v3...v3.7.0

Commits
  • e33196f Do not ivalidate the cache entirely on lock file change (#744)
  • c6722d3 update doc for frozen lock file (#789)
  • 8170e22 Detect cached folders from multiple directories (#735)
  • 698d505 Fix description about ensuring workflow access to private package (#704)
  • 869f4dd Merge pull request #758 from akv-platform/remove-implicit-dependencies
  • 10efafc Update canary version in tests to an existing one
  • 7d16907 Add missing dependency
  • d0d39bd Move eslint-plugin-node to dev dependencies
  • 15a2477 Install eslint-plugin-node
  • 7598dbc Update configuration files
  • Additional commits viewable in compare view

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 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)

Bumps [actions/setup-node](https://github.com/actions/setup-node) from 3.6.0 to 3.7.0.
- [Release notes](https://github.com/actions/setup-node/releases)
- [Commits](actions/setup-node@64ed1c7...e33196f)

---
updated-dependencies:
- dependency-name: actions/setup-node
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@charris charris added the 09 - Backport-Candidate PRs tagged should be backported label Jul 5, 2023
@charris charris merged commit 4b13692 into main Jul 5, 2023
@dependabot dependabot bot deleted the dependabot/github_actions/actions/setup-node-3.7.0 branch July 5, 2023 19:24
@charris charris removed the 09 - Backport-Candidate PRs tagged should be backported label Jul 5, 2023
seberg added a commit that referenced this pull request Jan 20, 2024
…r`` (#25409)

This reorganize how array-wrap is called. It might very mildly change the semantics for reductions I think (and for negative priorities).

Overall, it now passes a new return_scalar=False/True when calling __array_wrap__ and deprecates any array-wrap which does not accept arr, context, return_scalar.

I have not integrated it yet, but half the reason for the reorganization is to integrate it/reuse it in the array_coverter helper PR (gh-24214), which stumbled over trying to make the scalar handling sane.

Forcing downstream to add return_scalar=False to the signature is a bit annoying, but e.g. our memory maps currently try to guess at it, which seems bad. I am hoping, this can be part to making the scalar vs. array return more sane.

But, maybe mainly, I hope it consolidates things (together with gh-24124 mainly, as if ufuncs were the only complex place we used this, it wouldn't matter much).

---

* API: Reorganize `__array_wrap__` and add `return_scalar=False`

This also deprecates any `__array_wrap__` which does not accept
`context` and `return_scalar`.

* BUG: Fix niche bug in rounding.

* MAINT: Adjust __array_wrap__ in code and tests (also deprecation test)

* MAINT: Use/move the simplest C-wrapping also

* DOC: Update doc and add release note

* STY: Make linter happy in old tests

* MAINT: Silence GCC warning (value cannot really be used uninitialized)

* MAINT: Small style fixes

* BUG: Fix reference leak in ufunc array-wrapping

This probably doesn't fix the 32bit issue unfortunately, only the windows ones...

* BUG: Fix leak for result arrays in all ufunc calls

* Ensure we try passing context and address related smaller review comments

* Ensure we don't try `context=None` and expand code comment

* Rely on return_scalar always being right (and style nit)

* Remove outdated comments as per review

* Let's just undo force-wrap for now for reductions (its a change...)

* ENH: Chain the original error when the deprecationwarning is raised

Doing this due to gh-25635 since it is super confusing with the
bad retrying...

* BUG,MAINT: Address Martens review comments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant