Update all non-major dependencies #1646
Merged
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
requested review from
mike-winberry,
Racer159,
Noxsios,
jeff-mccoy and
YrrepNoj
as code owners
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: go.sum |
✅ Deploy Preview for zarf-docs canceled.
|
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
17 times, most recently
from
20ba913
to
39354cb
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
6 times, most recently
from
e1d4e24
to
d5c767b
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
12 times, most recently
from
f5354d3
to
fb12608
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
fb12608
to
044c5c0
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ Warning: custom changes will be lost. |
Noxsios
approved these changes
May 15, 2023
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.
This PR contains the following updates:
^0.0.47->^0.0.481.2.6->1.2.71.32.3->1.33.01.15.7->1.16.35.59.0->5.59.55.59.0->5.59.5v0.14.1->v0.14.2v0.4.3->v0.5.08.39.0->8.40.01.0.25->1.0.26v0.79.0->v0.80.0v0.27.3->v0.27.4v2.8.1+incompatible->v2.8.2+incompatiblev23.0.4+incompatible->v23.0.6+incompatiblev0.14.0->v0.15.1v23.0.4+incompatible->v23.0.6+incompatiblev1.1.0-rc2.0.20221005185240-3a7f492d3f1b->v1.1.0-rc3v2.3.0->v2.3.3v2.3.2->v2.3.3v0.8.0->v0.9.0v3.11.3->v3.12.0v0.26.4->v0.27.1v0.26.4->v0.27.1v0.26.4->v0.27.1v0.26.4->v0.27.1v2.90.1->v2.100.1v0.26.4->v0.27.1v2.0.2->v2.1.01.32.3->1.33.023.0.21->23.0.301.62.0->1.62.1v0.12.1->v0.13.43.58.0->3.59.13.2.0->3.3.24.3.1->4.3.5⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
Release Notes
floating-ui/floating-ui
v1.2.7Compare Source
Bug Fixes
fix(getClippingRect): incorrect clipping rect calculation with
position: fixedancestors (#2291)fix(autoUpdate): prevent
animationFrame: truefrom disabling visualViewport scrolling updates (#2303)Microsoft/playwright
v1.33.0Compare Source
Locators Update
Use [
locator.or()][locator.or()] to create a locator that matches either of the two locators.Consider a scenario where you'd like to click on a "New email" button, but sometimes a security settings dialog shows up instead.
In this case, you can wait for either a "New email" button, or a dialog and act accordingly:
Use new options
hasNotandhasNotTextin [locator.filter()][locator.filter()]to find elements that do not match certain conditions.
Use new web-first assertion [
locatorAssertions.toBeAttached()][locatorAssertions.toBeAttached()] to ensure that the elementis present in the page's DOM. Do not confuse with the [
locatorAssertions.toBeVisible()][locatorAssertions.toBeVisible()] that ensures thatelement is both attached & visible.
New APIs
locator.or()][locator.or()]hasNotin [locator.filter()][locator.filter()]hasNotTextin [locator.filter()][locator.filter()]locatorAssertions.toBeAttached()][locatorAssertions.toBeAttached()]timeoutin [route.fetch()][route.fetch()]reporter.onExit()][reporter.onExit()]mcr.microsoft.com/playwright:v1.33.0now serves a Playwright image based on Ubuntu Jammy.To use the focal-based image, please use
mcr.microsoft.com/playwright:v1.33.0-focalinstead.Browser Versions
This version was also tested against the following stable channels:
sveltejs/kit
v1.16.3Compare Source
Patch Changes
fix: entry generation with mixed segments (#9879)
fix: use
focusVisible: falseto prevent unwanted focus ring on navigation (#9861)v1.16.2Compare Source
Patch Changes
fix: support Node 20 (
6e2efcf62)fix: reset focus synchronously on navigation (#9837)
v1.16.1Compare Source
Patch Changes
fix: realign state.branch on the client on first load (#9754)
fix: update
$page.datacorrectly after invalidate (#9798)fix: file not found in manifest (#9846)
v1.16.0Compare Source
Minor Changes
export const entries(#9571)v1.15.11Compare Source
Patch Changes
chore: more compact representation for invalidated search param (#9708)
chore: fix import path to app script on windows (#9743)
fix: make $app/navigation more resilient to bundler reordering (#9808)
fix: page load
fetch()now accepts the same input types for the body as the native fetch function (#9801)fix: handle preload and filterSerializedResponseHeaders in sequence function (#9741)
v1.15.10Compare Source
Patch Changes
v1.15.9Compare Source
Patch Changes
fix: correctly replace state when
data-sveltekit-replacestateis used with a hash link (#9751)fix: compute trailing slash on page server / data request (#9738)
fix: update vite-plugin-svelte to fix windows resolution issue (#9769)
v1.15.8Compare Source
Patch Changes
chore: revert undici pin and upgrade version (#9740)
chore: upgrade vite-plugin-svelte for resolve improvements and warnings (#9742)
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v5.59.5Compare Source
Note: Version bump only for package @typescript-eslint/eslint-plugin
v5.59.2Compare Source
Note: Version bump only for package @typescript-eslint/eslint-plugin
v5.59.1Compare Source
Bug Fixes
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v5.59.5Compare Source
Note: Version bump only for package @typescript-eslint/parser
v5.59.2Compare Source
Note: Version bump only for package @typescript-eslint/parser
v5.59.1Compare Source
Note: Version bump only for package @typescript-eslint/parser
anchore/sbom-action
v0.14.2Compare Source
Changes in v0.14.2
output-file(#411) [gszr]cue-lang/cue
v0.5.0Compare Source
This release focuses on changes to the implementation of comprehensions, the algorithm for detecting cycles in CUE, and the reimplementation of
letcomprehensions as fields.Also included are a number of bug fixes and changes to help the KubeVela project upgrade off CUE v0.2.2 to the latest release. v0.5.0 is the first release since v0.4.3 back in April 2022. It has been a long time in the making, and is comprised of 277 commits.
It is worth noting that we do not plan nor wish for such long gaps between releases. For more details on upcoming releases and steps we are taking to increase release cadence as well as our confidence in each release, please see this discussion.
As a reminder: users can register their projects with
unity, our regression and performance testing setup.unityis used to ensure that a project's CUE evaluations do not unexpectedly stop working, or regress in terms of performance.unitycontinues to catch multiple issues with each release. Adding your project tounitynot only guarantees that we will not break your tests (if we do, we will work with you to fix your CUE code), but it also helps to improve the quality of each CUE release. We are currently in the process of releasing Unity as a GitHub App on the public Marketplace. Sign up to receive updates; we will be in touch as soon as the GitHub App is ready.Thank you to @djosephsen, @joaopapereira, @mpvl, @mvdan, @myitcv, @qequ, @rogpeppe, @rytswd, @satotake, @spachava753, and @tmm1 for contributing to this release!
Project-level changes
Various CI-related changes have been made to simplify and streamline the GerritHub-based CI setup across the various CUE repositories. A common
basepackage is vendored into each repository and used as a template for GitHub workflows and other configuration. For those interested in studying the setup, please see the files beneathinternal/ci.This release drops support for
go1.16.x,go1.17.xandgo1.18.x, is tested againstgo1.19.xandgo1.20.x, and is built usinggo1.20.2.Our dependency on
github.com/rogpeppe/go-internalis upgraded tov1.9.0and varioustestscript-related improvements have been made to CUE's tests.GoReleaser has been upgrade to v1.16.2 as part of the release workflow. In a related change, CL 546920 moves us to a CUE-based source configuration for GoReleaser. This allows us to define the concept of 'latest', state which indicates whether we should perform the homebrew release and the Docker manifest latest steps. This fixes a long-standing bug whereby homebrew taps and Docker images were created for the latest release, regardless of whether that was a pre-release, or indeed a patch version of a non-current minor version.
As of CL 547507, CUE build artefacts published on GitHub are entirely reproducible, thanks to Go's support for reproducible, verifiable and verified builds.
Encoders
When
cue import-ing YAML, the-Rrecursive flag now only recursively interprets text as YAML if it contains a newline CL 536902.API
Various APIs have been transitioned to drop use of the deprecated
cue.Runtimetype, as well as migrating away fromcue.Instanceviacue.InstanceOrValue. Some use of these deprecated types remains: #1035, #1735, #1806. These will be tidied up in later releases as the API surface matures towards v1.0.0.The
cuepackage now supportsInlineImportsforValue.SyntaxCL 541561. This leverages new support within the internal exporter to creating self-contained CUE. This change also deprecatesValue.ResolveReferences().Package
cueaddsSelector.Typeto make it easier to pull out selector-specific information from a selector (for example, it makes it possible and cheap to retrieve the unquoted string label from a regular field selector) CL 542738.Package
cueaddsValue.BuildInstance(). If acue.Valueexactly represents a package,BuildInstance()returns the build instance corresponding to the value CL 542769.cue/statsis introduced as a new package for getting CUE operation statistics. The functionality is hoisted frominternal/core/adt, but the package should for all practical purposes be seen as a new implementation. The stats have been aggregated as experimental functionality to thetools/flowpackage.CL 546763 disallowed deprecated language features in the Go API. These features had long been deprecated in
cmd/cue. This means that API operations will now fail on deprecated features whereas before they were handled in compatibility mode. Theparser.FromVersionfeature can be used to reenable these deprecated features.Language
This release does not introduce any language changes. CL 537264 made some minor adjustments to the language specification to improve readability.
CL 541457 removes support for re-writing of old-style
letdeclarations. This had already been deprecated for a long time and this change was made to enable support for aliases of embeddings.Core evaluator
Per-field comprehensions
One of the major changes introduced in this release is how comprehensions are handled. CL 529524 move the evaluator to a model of per-field comprehensions.
Comprehensions are expanded
for,if, andletclauses that yield zero or more structs to be embedded in the enclosing list or struct.CUE does not allow cyclic dependencies between comprehensions if they result in an ambiguous set of fields. It does allow cascading insertions as in:
The way this works is that for fields with a fixed prefix path in a comprehension value, the comprehension is assigned to these respective fields.
More concretely, the above example is rewritten to:
where the fields with if clause are only inserted if their condition resolves to true. Note that this is not valid CUE; it may be in the future.
With this rewrite, dependencies in comprehension expressions are handled analogously to other expressions.
Note that a single comprehension may be distributed across multiple fields. The evaluator will ensure, however, that a comprehension is only evaluated once.
Analogous to reference cycles, as of CL 544129 we allow comprehensions to use the struct in which they are defined as source, as long as they do not introduce new fields, which would alter the source on which they iterate.
Reimplementation of cycle detection
The new algorithm is inspired by the cycle detection used by Tomabechi's 1 and Van Lohuizen's 2 graph unification algorithms.
Unlike with traditional graph unification, however, CUE uses references, which, unlike node equivalence, are unidirectional. This means that the technique to track equivalence through dereference, as common in graph unification algorithms like Tomabechi's, does not work unaltered.
The unidirectional nature of references imply that each reference equates an exact copy of the value it points to. This renders the original approach of node-pointer equivalence useless.
The new algorithm, a variant of Tomabechi's and Van Lohuizen's algorithm, looks at references equality on conjuncts, instead of node equality. This simplifies the accounting and allows for far simpler and precise accounting when using references instead of the traditional node equivalence.
More background info on cycles
We have to define when a cycle is detected. CUE implementations MUST report an error upon a structural cycle, and SHOULD report cycles at the shortest possible paths at which they occur, but MAY report these at deeper paths. For instance, the following CUE has a structural cycle:
The shortest path at which the cycle can be reported is
f.g, but as all failed configurations are logically equal, it is fine for implementations to report them atf.g.g, for instance.It is not, however, correct to assume that a reference to a parent is always a cycle. Consider this case:
Even though reference
arefers to a parent node, the cycle needs to be fed by a concrete field in structato persist, meaning it cannot result in a cycle as defined in the spec as it is defined here. Note however, that a specialization of this configuration can result in a cycle. ConsiderHere reference
ais guaranteed to result in a structural cycle, as fieldcwill match the pattern constraint unconditionally.In other words, it is not possible to exclude tracking references across pattern constraints from cycle checking.
It is tempting to try to find a complete set of these edge cases with the aim to statically determine cases in which this occurs. But as Carpenter [^Carpenter] demonstrates, it is possible for cycles to be created as a result of unifying two graphs that are themselves acyclic. The following example is a translation of Carpenters example to CUE:
Even though the above contains no cycles, the result of
x & yis cyclic:This means that, in practice, cycle detection has at least partially a dynamic component to it.
The language specification contains a higher-level and more complete overview of structural cycles.
Hideto Tomabechi. 1992. Quasi-Destructive Graph Unification with
Structure-Sharing. In COLING 1992 Volume 2: The 14th International
Conference on Computational Linguistics.
Marcel P. van Lohuizen. 2000. "Memory-Efficient and Thread-Safe
Quasi-Destructive Graph Unification". In Proceedings of the 38th Annual
Meeting of the Association for Computational Linguistics, pages 352–359,
Hong Kong. Association for Computational Linguistics.
[^Carpenter]:
Bob Carpenter, "The logic of typed feature structures."
Cambridge University Press, ISBN:0-521-41932-8
Reimplementation of
letcomprehensionsCL 543362 made a change to
internal/coreto reimplementletcomprehensions as fields. This makes it easier to track context asletcomprehensions then follow the same paradigm as fields. It also allows debug information to be shown as to where lets are added in the tree. This change was accompanied by number of others that refined the approach.Self-contained export
internal/core/exportnow implements an algorithm for generating self-contained CUE on export, an option that can further be refined by asking the exporter to inline imports. These internal changes manifest in changes tocue defandcuelang.org/go/cuethat are described elsewhere.Other changes
CL 545897 started tracking stats within the core CUE tests. This book keeping helps to spot likely regressions in performance early by collocating the stats with the CUE that is being evaluated.
Builtins
In the
strconvpackage,strconv.FormatIntandstrconv.FormatUintnow support arbitary-precision format; see CL 538512.CL 545898 improved the error messages for
pkgbuiltins, by including the path in error in many cases, and passing a wrapped message forencoding/yaml.CL 546237 allows incomplete
list.MinItemsconstraints. Before it either returnedfalseortrue, ignoring that making a configuration more specific might still satisfyMinItemslater on. CL 546238 made a similar change forstruct.MinFields.Tooling layer
Standard input is now parsed correctly in
cue cmd-declared command tasks; see CL 541898.cmd/cueVersion control system (VCS) information is included in
cue versionas of CL 540297. The Go version used to buildcmd/cueis included as of CL 549302.cue defnow supports an--inline-importsflag which resolves imports to print a self-contained version of the command input. For example, given thetxtarinput:The running
cue def --inline-imports in.cuewill give:CL 546243 fixed a long-standing bug whereby the
--ignoreerrors flag was not observed bycue eval.Changelog
d780488a1d9054af01db122156efa4403eb0eaee71584b21e7c076809f3af8f390bca5a14fbf4be0601bby @myitcv inf4d04a7374a2ccc0421b41ce912087c79ef28321f65d42c6c3ba76ba576d0e4ca411de89693e19b1f24863749fed573e0c352a7365a6bd19Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.
Footnotes
https://aclanthology.org/C92-2068 ↩
https://aclanthology.org/P00-1045/ ↩