ibm-messaging / kafka-java-vertx-starter

Starter Java app for testing connection to Apache Kafka with Vert.x
Apache License 2.0
44 stars 32 forks source link

build(deps): Bump @carbon/themes from 10.36.0 to 11.12.0 in /ui #336

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps @carbon/themes from 10.36.0 to 11.12.0.

Release notes

Sourced from @​carbon/themes's releases.

v11.12.0

v11.12.0 (2022-9-1)

carbon-components-react@8.12.0

Housekeeping :house:

carbon-components@11.12.0

Housekeeping :house:

@carbon/cli@11.3.0

Housekeeping :house:

  • chore(deps): update verdaccio/verdaccio docker tag to v5 (#11984) (b6a0d4a1e)

@carbon/elements@11.9.0

Housekeeping :house:

@carbon/pictograms-react@11.31.0

Housekeeping :house:

@carbon/pictograms@12.5.0

New features :rocket:

Housekeeping :house:

@carbon/react@1.12.0

New features :rocket:

  • feat(FluidTextInput): create unstable__FluidTextInput component (#11971) (58b30d39f)
  • feat(TreeView): publish single select tree (#11938) (c520c3be6)

Bug fixes :bug:

... (truncated)

Changelog

Sourced from @​carbon/themes's changelog.

Release

How we version and release packages in the Design System

Table of Contents

Overview

The Design System follows a time-based release model where we deliver a stable minor update every two weeks. The full schedule for releases is available here.

We also publish prereleases before every minor release. This prerelease happens several days before the stable release. This offers an integration window where the prerelease can be tested on products before the stable release.

We also ship security and bug fixes in patch releases. This will be shipped as-needed and do not follow a specific schedule.

Release Team

The release team is responsible for coordinating the minor and patch releases for the Design System in a given week. This group is composed of a release lead and sidekick. The release lead is responsible for:

  • Managing the release itself, including
    • Testing
    • Publishing
    • Support
  • Helping the release sidekick understand and run through the release process, where appropriate

The release sidekick is responsible for:

... (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 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] commented 1 year ago

Superseded by #341.