Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Renovate Update Patch & Minor Updates #475

Merged
merged 1 commit into from
Jul 30, 2024
Merged

Renovate Update Patch & Minor Updates #475

merged 1 commit into from
Jul 30, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 3, 2024 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
anothrNick/github-tag-action action minor 1.69.0 -> 1.70.0 age adoption passing confidence
cypress (source) devDependencies minor 13.12.0 -> 13.13.1 age adoption passing confidence
cypress/included final minor 13.12.0 -> 13.13.1 age adoption passing confidence
esbuild devDependencies minor ^0.21.0 -> ^0.23.0 age adoption passing confidence
eslint (source) devDependencies minor 9.6.0 -> 9.8.0 age adoption passing confidence
github.com/ministryofjustice/opg-go-common require minor v1.4.0 -> v1.8.0 age adoption passing confidence
go.opentelemetry.io/contrib/detectors/aws/ecs require minor v1.27.0 -> v1.28.0 age adoption passing confidence
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp require minor v0.52.0 -> v0.53.0 age adoption passing confidence
go.opentelemetry.io/contrib/propagators/aws require minor v1.27.0 -> v1.28.0 age adoption passing confidence
go.opentelemetry.io/otel require minor v1.27.0 -> v1.28.0 age adoption passing confidence
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc require minor v1.27.0 -> v1.28.0 age adoption passing confidence
go.opentelemetry.io/otel/sdk require minor v1.27.0 -> v1.28.0 age adoption passing confidence
govuk-frontend (source) dependencies patch 5.4.0 -> 5.4.1 age adoption passing confidence
node stage minor 20.15.0-alpine3.20 -> 20.16.0-alpine3.20 age adoption passing confidence
prettier (source) devDependencies patch 3.3.2 -> 3.3.3 age adoption passing confidence
sass devDependencies patch 1.77.6 -> 1.77.8 age adoption passing confidence

Release Notes

anothrNick/github-tag-action (anothrNick/github-tag-action)

v1.70.0

Compare Source

What's Changed

New Contributors

Full Changelog: anothrNick/github-tag-action@1...1.70.0

cypress-io/cypress (cypress)

v13.13.1

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#13-13-1

v13.13.0

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#13-13-0

evanw/esbuild (esbuild)

v0.23.0

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.22.0 or ~0.22.0. See npm's documentation about semver for more information.

  • Revert the recent change to avoid bundling dependencies for node (#​3819)

    This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.

    I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.

    In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.

  • Fix preserving collapsed JSX whitespace (#​3818)

    When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with --jsx=preserve. Here is an example:

    // Original code
<Foo>
  <Bar />
</Foo>

// Old output (with --jsx=preserve)
<Foo><Bar /></Foo>;

// New output (with --jsx=preserve)
<Foo>
  <Bar />
</Foo>;

v0.22.0

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.21.0 or ~0.21.0. See npm's documentation about semver for more information.

  • Omit packages from bundles by default when targeting node (#​1874, #​2830, #​2846, #​2915, #​3145, #​3294, #​3323, #​3582, #​3809, #​3815)

    This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.

    With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.

    The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).

  • Drop support for older platforms (#​3802)

    This release drops support for the following operating systems:

    • Windows 7
    • Windows 8
    • Windows Server 2008
    • Windows Server 2012

    This is because the Go programming language dropped support for these operating system versions in Go 1.21, and this release updates esbuild from Go 1.20 to Go 1.22.

    Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.21). That might look something like this:

    git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild.exe --version

    In addition, this release increases the minimum required node version for esbuild's JavaScript API from node 12 to node 18. Node 18 is the oldest version of node that is still being supported (see node's release schedule for more information). This increase is because of an incompatibility between the JavaScript that the Go compiler generates for the esbuild-wasm package and versions of node before node 17.4 (specifically the crypto.getRandomValues function).

  • Update await using behavior to match TypeScript

    TypeScript 5.5 subtly changes the way await using behaves. This release updates esbuild to match these changes in TypeScript. You can read more about these changes in microsoft/TypeScript#58624.

  • Allow es2024 as a target environment

    The ECMAScript 2024 specification was just approved, so it has been added to esbuild as a possible compilation target. You can read more about the features that it adds here: https://2ality.com/2024/06/ecmascript-2024.html. The only addition that's relevant for esbuild is the regular expression /v flag. With --target=es2024, regular expressions that use the /v flag will now be passed through untransformed instead of being transformed into a call to new RegExp.

  • Publish binaries for OpenBSD on 64-bit ARM (#​3665, #​3674)

    With this release, you should now be able to install the esbuild npm package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1 chip.

    This was contributed by @​ikmckenz.

  • Publish binaries for WASI (WebAssembly System Interface) preview 1 (#​3300, #​3779)

    The upcoming WASI (WebAssembly System Interface) standard is going to be a way to run WebAssembly outside of a JavaScript host environment. In this scenario you only need a .wasm file without any supporting JavaScript code. Instead of JavaScript providing the APIs for the host environment, the WASI standard specifies a "system interface" that WebAssembly code can access directly (e.g. for file system access).

    Development versions of the WASI specification are being released using preview numbers. The people behind WASI are currently working on preview 2 but the Go compiler has released support for preview 1, which from what I understand is now considered an unsupported legacy release. However, some people have requested that esbuild publish binary executables that support WASI preview 1 so they can experiment with them.

    This release publishes esbuild precompiled for WASI preview 1 to the @esbuild/wasi-preview1 package on npm (specifically the file @esbuild/wasi-preview1/esbuild.wasm). This binary executable has not been tested and won't be officially supported, as it's for an old preview release of a specification that has since moved in another direction. If it works for you, great! If not, then you'll likely have to wait for the ecosystem to evolve before using esbuild with WASI. For example, it sounds like perhaps WASI preview 1 doesn't include support for opening network sockets so esbuild's local development server is unlikely to work with WASI preview 1.

  • Warn about onResolve plugins not setting a path (#​3790)

    Plugins that return values from onResolve without resolving the path (i.e. without setting either path or external: true) will now cause a warning. This is because esbuild only uses return values from onResolve if it successfully resolves the path, and it's not good for invalid input to be silently ignored.

  • Add a new Go API for running the CLI with plugins (#​3539)

    With esbuild's Go API, you can now call cli.RunWithPlugins(args, plugins) to pass an array of esbuild plugins to be used during the build process. This allows you to create a CLI that behaves similarly to esbuild's CLI but with additional Go plugins enabled.

    This was contributed by @​edewit.

eslint/eslint (eslint)

v9.8.0

Compare Source

v9.7.0

Compare Source

Features

  • 7bd9839 feat: add support for es2025 duplicate named capturing groups (#​18630) (Yosuke Ota)
  • 1381394 feat: add regex option in no-restricted-imports (#​18622) (Nitin Kumar)

Bug Fixes

  • 14e9f81 fix: destructuring in catch clause in no-unused-vars (#​18636) (Francesco Trotta)

Documentation

  • 9f416db docs: Add Powered by Algolia label to the search. (#​18633) (Amaresh S M)
  • c8d26cb docs: Open JS Foundation -> OpenJS Foundation (#​18649) (Milos Djermanovic)
  • 6e79ac7 docs: loadESLint does not support option cwd (#​18641) (Francesco Trotta)

Chores

ministryofjustice/opg-go-common (github.com/ministryofjustice/opg-go-common)

v1.8.0

Compare Source

v1.7.0

Compare Source

v1.6.0

Compare Source

v1.5.0

Compare Source

open-telemetry/opentelemetry-go-contrib (go.opentelemetry.io/contrib/detectors/aws/ecs)

v1.28.0: /v0.53.0/v0.22.0/v0.8.0/v0.3.0/v0.1.0

Compare Source

Overview
Added
  • Add the new go.opentelemetry.io/contrib/detectors/azure/azurevm package to provide a resource detector for Azure VMs. (#​5422)
  • Add support to configure views when creating MeterProvider using the config package. (#​5654)
  • The go.opentelemetry.io/contrib/config add support to configure periodic reader interval and timeout. (#​5661)
  • Add log support for the autoexport package. (#​5733)
  • Add support for disabling the old runtime metrics using the OTEL_GO_X_DEPRECATED_RUNTIME_METRICS=false environment variable. (#​5747)
  • Add support for signal-specific protocols environment variables (OTEL_EXPORTER_OTLP_TRACES_PROTOCOL, OTEL_EXPORTER_OTLP_LOGS_PROTOCOL, OTEL_EXPORTER_OTLP_METRICS_PROTOCOL) in go.opentelemetry.io/contrib/exporters/autoexport. (#​5816)
  • The go.opentelemetry.io/contrib/processors/minsev module is added.
    This module provides and experimental logging processor with a configurable threshold for the minimum severity records must have to be recorded. (#​5817)
  • The go.opentelemetry.io/contrib/processors/baggagecopy module.
    This module is a replacement of go.opentelemetry.io/contrib/processors/baggage/baggagetrace. (#​5824)
Changed
  • Improve performance of go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc with the usage of WithAttributeSet() instead of WithAttribute(). (#​5664)
  • Improve performance of go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp with the usage of WithAttributeSet() instead of WithAttribute(). (#​5664)
  • Update go.opentelemetry.io/contrib/config to latest released configuration schema which introduces breaking changes where Attributes is now a map[string]interface{}. (#​5758)
  • Upgrade all dependencies of go.opentelemetry.io/otel/semconv/v1.25.0 to go.opentelemetry.io/otel/semconv/v1.26.0. (#​5847)
Fixed
  • Custom attributes targeting metrics recorded by the go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp are not ignored anymore. (#​5129)
  • The double setup in go.opentelemetry.io/contrib/instrumentation/net/http/httptrace/otelhttptrace/example that caused duplicate traces. (#​5564)
  • The superfluous response.WriteHeader call in go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp when the response writer is flushed. (#​5634)
  • Use c.FullPath() method to set http.route attribute in go.opentelemetry.io/contrib/instrumentation/github.com/gin-gonic/gin/otelgin. (#​5734)
  • Out-of-bounds panic in case of invalid span ID in go.opentelemetry.io/contrib/propagators/b3. (#​5754)
Deprecated
  • The go.opentelemetry.io/contrib/instrumentation/github.com/labstack/echo/otelecho package is deprecated.
    If you would like to become a Code Owner of this module and prevent it from being removed, see #​5550. (#​5645)
  • The go.opentelemetry.io/contrib/instrumentation/gopkg.in/macaron.v1/otelmacaron package is deprecated.
    If you would like to become a Code Owner of this module and prevent it from being removed, see #​5552. (#​5646)
  • The go.opentelemetry.io/contrib/samplers/aws/xray package is deprecated.
    If you would like to become a Code Owner of this module and prevent it from being removed, see #​5554. (#​5647)
  • The go.opentelemetry.io/contrib/processors/baggage/baggagetrace package is deprecated.
    Use the added go.opentelemetry.io/contrib/processors/baggagecopy package instead. (#​5824)
    • Use baggagecopy.NewSpanProcessor as a replacement for baggagetrace.New.
      • NewSpanProcessor accepts a Fitler function type that selects which baggage members are added to a span.
      • NewSpanProcessor returns a *baggagecopy.SpanProcessor instead of a trace.SpanProcessor interface.
        The returned type still implements the interface.
What's Changed

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added dependencies Pull requests that update a dependency file Renovate labels Jul 3, 2024
@renovate renovate bot requested review from a team as code owners July 3, 2024 23:02
@github-actions GitHub Actions
Copy link

github-actions bot commented Jul 3, 2024 •
edited
Loading

Unit Test Results

438 tests  ±0   438 ✅ ±0   0s ⏱️ ±0s
  7 suites ±0     0 💤 ±0 
  1 files   ±0     0 ❌ ±0 

Results for commit 46516c8. ± Comparison against base commit 9ed2000.

♻️ This comment has been updated with latest results.

@renovate renovate bot force-pushed the renovate-all-minor-patch-updates branch 2 times, most recently from add10d6 to f32ad62 Compare July 4, 2024 20:08
@renovate renovate bot changed the title Renovate Update dependency esbuild to ^0.22.0 Renovate Update Patch & Minor Updates Jul 4, 2024
@renovate renovate bot force-pushed the renovate-all-minor-patch-updates branch 11 times, most recently from b655b92 to e0a967e Compare July 11, 2024 17:43
@renovate renovate bot force-pushed the renovate-all-minor-patch-updates branch 11 times, most recently from b5b51dd to 6f64386 Compare July 19, 2024 01:55
@renovate renovate bot force-pushed the renovate-all-minor-patch-updates branch 5 times, most recently from edc5e0e to 9382da5 Compare July 23, 2024 04:59
@renovate renovate bot force-pushed the renovate-all-minor-patch-updates branch 4 times, most recently from e70c8ab to 98d7154 Compare July 29, 2024 16:19
@renovate renovate bot force-pushed the renovate-all-minor-patch-updates branch from 98d7154 to 46516c8 Compare July 29, 2024 21:30
@kate-49 kate-49 merged commit 6f7a1ce into main Jul 30, 2024
8 checks passed
@kate-49 kate-49 deleted the renovate-all-minor-patch-updates branch July 30, 2024 08:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@kate-49 kate-49 kate-49 approved these changes

Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file Renovate
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@kate-49