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.

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

Update appcat #214

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update appcat #214

wants to merge 1 commit into from

Conversation

vshn-renovate
Copy link
Collaborator

@vshn-renovate vshn-renovate commented Aug 30, 2023

This PR contains the following updates:

Package Update Change
crossplane (source) minor 1.16.0 -> 1.18.2
mariadb (source) minor 14.0.10 -> 14.1.4
minio (source) minor 5.0.13 -> 5.3.0
nextcloud (source) minor 6.2.4 -> 6.5.1
redis (source) minor 17.7.1 -> 17.17.1

Release Notes

crossplane/crossplane (crossplane)

v1.18.2

Compare Source

This is a patch release scoped to fixing issues reported by users of Crossplane v1.17 and fixing security related issues in Crossplane's dependencies.

Users of v1.18.x reported that they were no longer able to downgrade a Crossplane installation from v1.18.x to a previous v1.17.x version. This was fixed in https://github.com/crossplane/crossplane/pull/6157 and we expect downgrades from v1.18.2 to be working once again.

The way Usage objects are managed within a Composition has been updated in https://github.com/crossplane/crossplane/pull/6155 to prevent orphaned Usage objects from remaining in the control plane when a Composition that creates a Usage is updated. The change is described below:

  • When the Usage itself deleted, the usage controller will wait for using resource before removing the finalizer, only if the Usage is part of a composite (i.e has crossplane.io/composite label).
  • When a resource removed from a composition (i.e. decomposed), the composition controllers (both PT and function) will remove the composed resource labels before deleting the resource.
  • This behavior is visually summarized in https://github.com/crossplane/crossplane/issues/5880#issuecomment-2363433313

What's Changed

Full Changelog: crossplane/crossplane@v1.18.1...v1.18.2

v1.18.1

Compare Source

What's Changed

Full Changelog: crossplane/crossplane@v1.18.0...v1.18.1

v1.18.0

Compare Source

🚨 Breaking Changes

  • While the EnvironmentConfig API was matured to Beta in this release, it's important to note that native support for EnvironmentConfig within a Composition was removed in https://github.com/crossplane/crossplane/pull/5938.
    • Users that enabled Alpha Composition Environments (--enable-environment-configs) and leveraged the native functionality (spec.environment.patches, spec.environment.environmentConfigs and *Environment patches), will have to migrate to Composition Functions to continue doing so.
    • We have built automated migration tooling to help with this migration/transition.
    • Further information, including migration instructions, can be found in the Crossplane docs.

❗ Notable Changes

A forthcoming change to Crossplane's default xpkg.upbound.io package registry may require you to authenticate to pull packages. In this release we've introduced a new ImageConfig API that makes it easier to configure registry credentials.

In order to minimize disruption to the community, we're making an exception to Crossplane's feature maturity process. We've introduced the new ImageConfig API as a beta feature that is enabled by default. We've also back ported the new ImageConfig API to the latest v1.16 and v1.17 patch releases.

🎉 Highlights

Release MVP

We'd like to thank @​cychiang for their multiple contributions within this release. Of particular note, they implemented #​5976 which enabled passing credentials to functions from the render command. We are also looking forward to including their contribution from #​5963 in the next milestone. Thanks @​cychiang!! 🙇‍♂️

📖 Full Changelog

New Contributors

Full Changelog: crossplane/crossplane@v1.17.0...v1.18.0

v1.17.4

Compare Source

This is a patch release scoped to fixing security related issues in Crossplane's dependencies, as well as improving E2E test reliability.

What's Changed

Full Changelog: crossplane/crossplane@v1.17.3...v1.17.4

v1.17.3

Compare Source

Notable Changes

A forthcoming change to Crossplane's default http://xpkg.upbound.io/ package registry may require you to authenticate to pull packages. In this release we've introduced a new ImageConfig API that makes it easier to configure registry credentials.

In order to minimize disruption to the community, we're making an exception to Crossplane's feature maturity process. We introduced the new ImageConfig API in Crossplane v1.18 as a beta feature that is enabled by default. We've also back ported the new ImageConfig API to this patch release, to make it available without needing to upgrade to v1.18.

What's Changed

Full Changelog: crossplane/crossplane@v1.17.2...v1.17.3

v1.17.2

Compare Source

This is a patch release scoped to fixing issues reported by users of Crossplane v1.17. First, this patch release addresses the below published security advisory that affects the versions of golang that Crossplane depends on.

Thank you @​aditya-mayo for reporting this vulnerability! 🙇‍♂️

This release also addresses an issue (https://github.com/crossplane/crossplane/issues/5971) where users of v1.17 were not able to build or install Functions using v1 package metadata. Now that Functions have matured to v1, this will become much more pervasive throughout the Crossplane Functions ecosystem.

What's Changed

Full Changelog: crossplane/crossplane@v1.17.1...v1.17.2

v1.17.1

Compare Source

This is a patch release scoped to fixing issues reported by users of Crossplane v1.17.

What's Changed

Full Changelog: crossplane/crossplane@v1.17.0...v1.17.1

v1.17.0

Compare Source

The v1.17.0 release is a regular quarterly Crossplane release that is focused on maturing a number of key areas of functionality across the project, as Crossplane continues to become more capable, more reliable, and more performant for your production workloads.

🎉 Highlights

  • New Contributors! This release has 14 new contributors! A huge thank you to all contributors as always.
  • Composition Functions graduation to v1: https://github.com/crossplane/crossplane/pull/5885 graduated Composition Functions to v1 while deprecating native patch and transform compositions. For a few releases, Crossplane will handle both beta and alpha composition Functions, and updated SDKs will be released soon.
  • Errors/Conditions on claims: It is now possible for Functions to communicate errors, events, and conditions up to the Claim level that occur during the execution of the composition function pipeline. Added with https://github.com/crossplane/crossplane/pull/5450, this means that consumers of Claims can get helpful and relevant observability into what may be happening with the composed resources underneath their claim. This keeps a strong separation of concerns still between Claims and Composite Resources, while providing useful curated information to the claim consumer that can help them drive to a resolution and a healthy resource on their own.
  • Cloud Change Logs: The runtime support for cloud change logs is included in the crossplane-runtime v1.17.0 release. Starting with this release, it will be possible for providers to track and log all changes they are making to their managed resources. You can expect new provider releases in the near future with this functionality enabled.
  • CLI updates:
    • crossplane beta render was promoted and is now available as crossplane render. Added support for render.crossplane.io/runtime-docker-cleanup to allow removing images after run if needed.
    • crossplane beta xpkg init was promoted too and is now available as crossplane xpkg init.
    • crossplane beta validate:
      • can now validate Crossplane resources and can also validate Functions' inputs against their schema.
      • can now catch unknown fields errors too.
      • is now able to download and cache the whole tree of transitive dependencies for a Package.
      • is now using a global cache directory in the home instead of creating one in the current directory.
    • crossplane beta trace is now much more performant for really deep dependency trees.

🚨 Warnings and breaking changes

  • Deprecated: Native patch and transform is now deprecated, see https://github.com/crossplane/crossplane/pull/5885
    • We don't plan to remove native patch and transform from Crossplane, but we no longer recommend using it. Use composition functions (mode: Pipeline) instead, as described in the updated documentation: https://docs.crossplane.io/latest/concepts/compositions/
    • As of Crossplane v1.17.0, development on native patch and transform will stop, and we'll only accept security related contributions to that part of the codebase.
  • crossplane CLI beta render and beta xpkg init were promoted to GA, meaning you no longer need to include the beta part of the command.

🏅 Release MVP

For our very first Crossplane "Release MVP", we're proud to select @​dalton-hill-0 for his thorough and useful contribution on https://github.com/crossplane/crossplane/pull/5450 to enable Claims to have selective errors/events/conditions surfaced to them. This has been functionality that the community desired for a long time and it really moves the needle on the end user developer/consumer experience with Crossplane. They will now be able to get relevant actionable information on their Claims to troubleshoot issues and get the infrastructure they need. Dalton did a great job of driving the complicated design and thinking through the edge cases with a critical eye on user experience throughout. Great work @​dalton-hill-0! 🙇‍♂️ 🏅

📖 Full Changelog


Configuration

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


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

This PR has been generated by Renovate Bot.

@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch from 49f730d to 11a6e18 Compare September 14, 2023 14:10
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch from 11a6e18 to dc206fa Compare September 30, 2023 21:19
@vshn-renovate vshn-renovate changed the title Update Helm release redis to v17.17.1 Update appcat Sep 30, 2023
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch from dc206fa to e31ed7c Compare October 6, 2023 12:58
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch 2 times, most recently from b0fdf84 to ae2d45b Compare October 9, 2023 15:38
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch from ae2d45b to 0d81b44 Compare October 14, 2023 08:30
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch from 0d81b44 to 557ea10 Compare December 5, 2023 10:21
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch from 557ea10 to 248889c Compare January 12, 2024 18:23
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch 3 times, most recently from 4a2cc7c to 19a1e7b Compare February 6, 2024 09:38
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch 5 times, most recently from 648b93a to 4559831 Compare February 22, 2024 17:38
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch 2 times, most recently from 51b991d to d79c7cb Compare March 3, 2024 18:58
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch from d79c7cb to e9783af Compare April 28, 2024 10:19
@vshn-renovate vshn-renovate changed the title Update appcat Update Helm release redis to v17.17.1 Jul 3, 2024
@vshn-renovate vshn-renovate changed the title Update Helm release redis to v17.17.1 Update appcat Jul 3, 2024
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch from e9783af to 74118f7 Compare July 4, 2024 11:19
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch 5 times, most recently from 44f061d to fc51207 Compare July 24, 2024 06:58
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch 5 times, most recently from b93317b to 1979aaf Compare July 29, 2024 15:19
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch from 1979aaf to c83ad0e Compare August 8, 2024 14:39
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch 2 times, most recently from e3014c9 to 778cbb1 Compare August 28, 2024 16:25
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch 3 times, most recently from 66715c2 to 2606b5f Compare September 12, 2024 19:41
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch from 2606b5f to a1a66c2 Compare September 16, 2024 23:41
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch from a1a66c2 to 662cc2c Compare October 11, 2024 13:01
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch from 662cc2c to 6714de6 Compare October 25, 2024 11:27
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch 2 times, most recently from 7f205a9 to 237ecef Compare November 5, 2024 10:22
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch 2 times, most recently from e73da30 to 32c9fc2 Compare November 20, 2024 12:36
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch 2 times, most recently from 9338a4c to c4fd684 Compare November 29, 2024 11:02
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch 2 times, most recently from 438f5d9 to b9b167a Compare December 10, 2024 20:15
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch 4 times, most recently from 362967a to 68325d5 Compare December 18, 2024 03:41
Signed-off-by: Renovate Bot <[email protected]>
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/appcat branch from 68325d5 to 0b6571a Compare December 19, 2024 22:37
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