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 #462

Merged
merged 1 commit into from
Jul 1, 2024
Merged

Renovate Update Patch & Minor Updates #462

merged 1 commit into from
Jul 1, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 18, 2024 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update Pending
cypress (source) 13.9.0 -> 13.12.0 age adoption passing confidence devDependencies minor
cypress/included 13.9.0 -> 13.12.0 age adoption passing confidence final minor
esbuild 0.21.2 -> 0.21.5 age adoption passing confidence devDependencies patch 0.22.0
github.com/ministryofjustice/opg-go-common v1.3.0 -> v1.4.0 age adoption passing confidence require minor
go.opentelemetry.io/contrib/detectors/aws/ecs v1.26.0 -> v1.27.0 age adoption passing confidence require minor
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.51.0 -> v0.52.0 age adoption passing confidence require minor
go.opentelemetry.io/contrib/propagators/aws v1.26.0 -> v1.27.0 age adoption passing confidence require minor
go.opentelemetry.io/otel v1.26.0 -> v1.27.0 age adoption passing confidence require minor
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.26.0 -> v1.27.0 age adoption passing confidence require minor
go.opentelemetry.io/otel/sdk v1.26.0 -> v1.27.0 age adoption passing confidence require minor
golangci/golangci-lint v1.58.1 -> v1.59.1 age adoption passing confidence minor
govuk-frontend (source) 5.3.1 -> 5.4.0 age adoption passing confidence dependencies minor
prettier (source) 3.2.5 -> 3.3.2 age adoption passing confidence devDependencies minor
sass 1.77.1 -> 1.77.6 age adoption passing confidence devDependencies patch

Release Notes

cypress-io/cypress (cypress)

v13.12.0

Compare Source

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

v13.11.0

Compare Source

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

v13.10.0

Compare Source

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

evanw/esbuild (esbuild)

v0.21.5

Compare Source

  • Fix Symbol.metadata on classes without a class decorator (#​3781)

    This release fixes a bug with esbuild's support for the decorator metadata proposal. Previously esbuild only added the Symbol.metadata property to decorated classes if there was a decorator on the class element itself. However, the proposal says that the Symbol.metadata property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.

  • Allow unknown import attributes to be used with the copy loader (#​3792)

    Import attributes (the with keyword on import statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load ./bagel.js as type bagel:

    // This is an error with "--bundle" without also using "--external:./bagel.js"
import tasty from "./bagel.js" with { type: "bagel" }

    Because of that, bundling this code with esbuild is an error unless the file ./bagel.js is external to the bundle (such as with --bundle --external:./bagel.js).

    However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the copy loader. That's because the copy loader behaves similarly to --external in that the file is left external to the bundle. The difference is that the copy loader copies the file into the output folder and rewrites the import path while --external doesn't. That means the following will now work with the copy loader (such as with --bundle --loader:.bagel=copy):

    // This is no longer an error with "--bundle" and "--loader:.bagel=copy"
import tasty from "./tasty.bagel" with { type: "bagel" }

  • Support import attributes with glob-style imports (#​3797)

    This release adds support for import attributes (the with option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:

    async function loadLocale(locale: string): Locale {
  const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
  return unpackLocale(locale, data)
}

    Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:

    ✘ [ERROR] No loader is configured for ".data" files: locales/en-US.data

    example.ts:2:28:
      2 │   const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
        ╵                             ~~~~~~~~~~~~~~~~~~~~~~~~~~

    In addition, this change means plugins can now access the contents of with for glob-style imports.

  • Support ${configDir} in tsconfig.json files (#​3782)

    This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence ${configDir} is now respected at the start of baseUrl and paths values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets base tsconfig.json files specified via extends refer to the directory of the top-level tsconfig.json file. Here is an example:

    {
  "compilerOptions": {
    "paths": {
      "js/*": ["${configDir}/dist/js/*"]
    }
  }
}

    You can read more in TypeScript's blog post about their upcoming 5.5 release. Note that this feature does not make use of template literals (you need to use "${configDir}/dist/js/*" not `${configDir}/dist/js/*`). The syntax for tsconfig.json is still just JSON with comments, and JSON syntax does not allow template literals. This feature only recognizes ${configDir} in strings for certain path-like properties, and only at the beginning of the string.

  • Fix internal error with --supported:object-accessors=false (#​3794)

    This release fixes a regression in 0.21.0 where some code that was added to esbuild's internal runtime library of helper functions for JavaScript decorators fails to parse when you configure esbuild with --supported:object-accessors=false. The reason is that esbuild introduced code that does { get [name]() {} } which uses both the object-extensions feature for the [name] and the object-accessors feature for the get, but esbuild was incorrectly only checking for object-extensions and not for object-accessors. Additional tests have been added to avoid this type of issue in the future. A workaround for this issue in earlier releases is to also add --supported:object-extensions=false.

v0.21.4

Compare Source

  • Update support for import assertions and import attributes in node (#​3778)

    Import assertions (the assert keyword) have been removed from node starting in v22.0.0. So esbuild will now strip them and generate a warning with --target=node22 or above:

    ▲ [WARNING] The "assert" keyword is not supported in the configured target environment ("node22") [assert-to-with]

    example.mjs:1:40:
      1 │ import json from "esbuild/package.json" assert { type: "json" }
        │                                         ~~~~~~
        ╵                                         with

  Did you mean to use "with" instead of "assert"?

    Import attributes (the with keyword) have been backported to node 18 starting in v18.20.0. So esbuild will no longer strip them with --target=node18.N if N is 20 or greater.

  • Fix for await transform when a label is present

    This release fixes a bug where the for await transform, which wraps the loop in a try statement, previously failed to also move the loop's label into the try statement. This bug only affects code that uses both of these features in combination. Here's an example of some affected code:

    // Original code
async function test() {
  outer: for await (const x of [Promise.resolve([0, 1])]) {
    for (const y of x) if (y) break outer
    throw 'fail'
  }
}

// Old output (with --target=es6)
function test() {
  return __async(this, null, function* () {
    outer: try {
      for (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp, error; more = !(temp = yield iter.next()).done; more = false) {
        const x = temp.value;
        for (const y of x) if (y) break outer;
        throw "fail";
      }
    } catch (temp) {
      error = [temp];
    } finally {
      try {
        more && (temp = iter.return) && (yield temp.call(iter));
      } finally {
        if (error)
          throw error[0];
      }
    }
  });
}

// New output (with --target=es6)
function test() {
  return __async(this, null, function* () {
    try {
      outer: for (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp, error; more = !(temp = yield iter.next()).done; more = false) {
        const x = temp.value;
        for (const y of x) if (y) break outer;
        throw "fail";
      }
    } catch (temp) {
      error = [temp];
    } finally {
      try {
        more && (temp = iter.return) && (yield temp.call(iter));
      } finally {
        if (error)
          throw error[0];
      }
    }
  });
}

  • Do additional constant folding after cross-module enum inlining (#​3416, #​3425)

    This release adds a few more cases where esbuild does constant folding after cross-module enum inlining.

    // Original code: enum.ts
export enum Platform {
  WINDOWS = 'windows',
  MACOS = 'macos',
  LINUX = 'linux',
}

// Original code: main.ts
import { Platform } from './enum';
declare const PLATFORM: string;
export function logPlatform() {
  if (PLATFORM == Platform.WINDOWS) console.log('Windows');
  else if (PLATFORM == Platform.MACOS) console.log('macOS');
  else if (PLATFORM == Platform.LINUX) console.log('Linux');
  else console.log('Other');
}

// Old output (with --bundle '--define:PLATFORM="macos"' --minify --format=esm)
function n(){"windows"=="macos"?console.log("Windows"):"macos"=="macos"?console.log("macOS"):"linux"=="macos"?console.log("Linux"):console.log("Other")}export{n as logPlatform};

// New output (with --bundle '--define:PLATFORM="macos"' --minify --format=esm)
function n(){console.log("macOS")}export{n as logPlatform};

  • Pass import attributes to on-resolve plugins (#​3384, #​3639, #​3646)

    With this release, on-resolve plugins will now have access to the import attributes on the import via the with property of the arguments object. This mirrors the with property of the arguments object that's already passed to on-load plugins. In addition, you can now pass with to the resolve() API call which will then forward that value on to all relevant plugins. Here's an example of a plugin that can now be written:

    const examplePlugin = {
  name: 'Example plugin',
  setup(build) {
    build.onResolve({ filter: /.*/ }, args => {
      if (args.with.type === 'external')
        return { external: true }
    })
  }
}

require('esbuild').build({
  stdin: {
    contents: `
      import foo from "./foo" with { type: "external" }
      foo()
    `,
  },
  bundle: true,
  format: 'esm',
  write: false,
  plugins: [examplePlugin],
}).then(result => {
  console.log(result.outputFiles[0].text)
})

  • Formatting support for the @position-try rule (#​3773)

    Chrome shipped this new CSS at-rule in version 125 as part of the CSS anchor positioning API. With this release, esbuild now knows to expect a declaration list inside of the @position-try body block and will format it appropriately.

  • Always allow internal string import and export aliases (#​3343)

    Import and export names can be string literals in ES2022+. Previously esbuild forbid any usage of these aliases when the target was below ES2022. Starting with this release, esbuild will only forbid such usage when the alias would otherwise end up in output as a string literal. String literal aliases that are only used internally in the bundle and are "compiled away" are no longer errors. This makes it possible to use string literal aliases with esbuild's inject feature even when the target is earlier than ES2022.

v0.21.3

Compare Source

  • Implement the decorator metadata proposal (#​3760)

    This release implements the decorator metadata proposal, which is a sub-proposal of the decorators proposal. Microsoft shipped the decorators proposal in TypeScript 5.0 and the decorator metadata proposal in TypeScript 5.2, so it's important that esbuild also supports both of these features. Here's a quick example:

    // Shim the "Symbol.metadata" symbol
Symbol.metadata ??= Symbol('Symbol.metadata')

const track = (_, context) => {
  (context.metadata.names ||= []).push(context.name)
}

class Foo {
  @​track foo = 1
  @​track bar = 2
}

// Prints ["foo", "bar"]
console.log(Foo[Symbol.metadata].names)

    ⚠️ WARNING ⚠️

    This proposal has been marked as "stage 3" which means "recommended for implementation". However, it's still a work in progress and isn't a part of JavaScript yet, so keep in mind that any code that uses JavaScript decorator metadata may need to be updated as the feature continues to evolve. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.

  • Fix bundled decorators in derived classes (#​3768)

    In certain cases, bundling code that uses decorators in a derived class with a class body that references its own class name could previously generate code that crashes at run-time due to an incorrect variable name. This problem has been fixed. Here is an example of code that was compiled incorrectly before this fix:

    class Foo extends Object {
  @​(x => x) foo() {
    return Foo
  }
}
console.log(new Foo().foo())

  • Fix tsconfig.json files inside symlinked directories (#​3767)

    This release fixes an issue with a scenario involving a tsconfig.json file that extends another file from within a symlinked directory that uses the paths feature. In that case, the implicit baseURL value should be based on the real path (i.e. after expanding all symbolic links) instead of the original path. This was already done for other files that esbuild resolves but was not yet done for tsconfig.json because it's special-cased (the regular path resolver can't be used because the information inside tsconfig.json is involved in path resolution). Note that this fix no longer applies if the --preserve-symlinks setting is enabled.

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

v1.4.0

Compare Source

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

v1.27.0: /v0.52.0/v0.21.0/v0.7.0/v0.2.0

Compare Source

Overview

Added
  • Add the new go.opentelemetry.io/contrib/instrgen package to provide auto-generated source code instrumentation. (#​3068, #​3108)
  • Add an experimental OTEL_METRICS_PRODUCERS environment variable to go.opentelemetry.io/contrib/autoexport to be set metrics producers. (#​5281)
    • prometheus and none are supported values. You can specify multiple producers separated by a comma.
    • Add WithFallbackMetricProducer option that adds a fallback if the OTEL_METRICS_PRODUCERS is not set or empty.
  • The go.opentelemetry.io/contrib/processors/baggage/baggagetrace module. This module provides a Baggage Span Processor. (#​5404)
  • Add gRPC trace Filter for stats handler to go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc. (#​5196)
  • Add a repository Code Ownership Policy. (#​5555)
  • The go.opentelemetry.io/contrib/bridges/otellogrus module. This module provides an OpenTelemetry logging bridge for github.com/sirupsen/logrus. (#​5355)
  • The WithVersion option function in go.opentelemetry.io/contrib/bridges/otelslog. This option function is used as a replacement of WithInstrumentationScope to specify the logged package version. (#​5588)
  • The WithSchemaURL option function in go.opentelemetry.io/contrib/bridges/otelslog. This option function is used as a replacement of WithInstrumentationScope to specify the semantic convention schema URL for the logged records. (#​5588)
  • Add support for Cloud Run jobs in go.opentelemetry.io/contrib/detectors/gcp. (#​5559)
Changed

  • The gRPC trace Filter for interceptor is renamed to InterceptorFilter. (#​5196)

  • The gRPC trace filter functions Any, All, None, Not, MethodName, MethodPrefix, FullMethodName, ServiceName, ServicePrefix and HealthCheck for interceptor are moved to go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc/filters/interceptor. With this change, the filters in go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc are now working for stats handler. (#​5196)

  • NewLogger now accepts a name string as the first argument. This parameter is used as a replacement of WithInstrumentationScope to specify the name of the logger backing the underlying Handler. (#​5588)

  • NewHandler now accepts a name string as the first argument. This parameter is used as a replacement of WithInstrumentationScope to specify the name of the logger backing the returned Handler. (#​5588)

  • Upgrade all dependencies of go.opentelemetry.io/otel/semconv/v1.24.0 to go.opentelemetry.io/otel/semconv/v1.25.0. (#​5605)

Removed
  • The WithInstrumentationScope option function in go.opentelemetry.io/contrib/bridges/otelslog is removed. Use the name parameter added to NewHandler and NewLogger as well as WithVersion and WithSchema as replacements. (#​5588)
Deprecated
  • The InterceptorFilter type in go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc is deprecated. (#​5196)

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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot requested review from a team as code owners May 18, 2024 00:17
@renovate renovate bot added dependencies Pull requests that update a dependency file Renovate labels May 18, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented May 18, 2024 •
edited
Loading

Unit Test Results

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

Results for commit bbc3145. ± Comparison against base commit e71c8ae.

♻️ This comment has been updated with latest results.

@renovate renovate bot force-pushed the renovate-all-minor-patch-updates branch from 0e734b9 to a74cbb7 Compare May 18, 2024 23:21
@renovate renovate bot changed the title Renovate Update module google.golang.org/grpc to v1.64.0 Renovate Update Patch & Minor Updates May 18, 2024
@renovate renovate bot force-pushed the renovate-all-minor-patch-updates branch 10 times, most recently from 92d4ec3 to d3273a5 Compare May 24, 2024 22:09
@renovate renovate bot force-pushed the renovate-all-minor-patch-updates branch 7 times, most recently from 1c2621e to d640cd1 Compare June 3, 2024 00:37
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Jun 4, 2024 •
edited
Loading

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 11 additional dependencies were updated

Details:

Package Change
github.com/brunoscheufler/aws-ecs-metadata-go v0.0.0-20220812150832-b6b31c6eeeaf -> v0.0.0-20221221133751-67e37ae746cd
github.com/grpc-ecosystem/grpc-gateway/v2 v2.19.1 -> v2.20.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.26.0 -> v1.27.0
go.opentelemetry.io/otel/metric v1.26.0 -> v1.27.0
go.opentelemetry.io/otel/trace v1.26.0 -> v1.27.0
golang.org/x/net v0.23.0 -> v0.25.0
golang.org/x/sys v0.19.0 -> v0.20.0
golang.org/x/text v0.14.0 -> v0.15.0
google.golang.org/genproto/googleapis/api v0.0.0-20240318140521-94a12d6c2237 -> v0.0.0-20240520151616-dc85e6b867a5
google.golang.org/genproto/googleapis/rpc v0.0.0-20240401170217-c3f982113cda -> v0.0.0-20240515191416-fc5f0ca64291
google.golang.org/protobuf v1.33.0 -> v1.34.1

@renovate renovate bot force-pushed the renovate-all-minor-patch-updates branch 5 times, most recently from 33269e0 to d871408 Compare June 7, 2024 10:47
@renovate renovate bot force-pushed the renovate-all-minor-patch-updates branch 6 times, most recently from 2df28eb to b0433ff Compare June 13, 2024 13:20
@renovate renovate bot force-pushed the renovate-all-minor-patch-updates branch 2 times, most recently from 36077bc to 0109754 Compare June 20, 2024 21:17
@renovate renovate bot force-pushed the renovate-all-minor-patch-updates branch from 0109754 to bbc3145 Compare June 22, 2024 08:47
@kate-49 kate-49 merged commit acd5c46 into main Jul 1, 2024
8 checks passed
@kate-49 kate-49 deleted the renovate-all-minor-patch-updates branch July 1, 2024 08:54
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.

None yet
1 participant
@kate-49