Skip to content

fix(deps): update module github.com/openmcp-project/project-workspace-operator/api to v2#23

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github.com-openmcp-project-project-workspace-operator-api-2.x
Open

fix(deps): update module github.com/openmcp-project/project-workspace-operator/api to v2#23
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github.com-openmcp-project-project-workspace-operator-api-2.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Apr 27, 2026

This PR contains the following updates:

Package Type Update Change OpenSSF
github.com/openmcp-project/project-workspace-operator/api require major v1.3.0v2.0.1 OpenSSF Scorecard

Release Notes

openmcp-project/project-workspace-operator (github.com/openmcp-project/project-workspace-operator/api)

v2.0.1

Compare Source

Changelog

🐛 Bugfixes

[USER]
  • Workspace and ManagedControlPlaneV2 resources should now have the correct api group set in the project/workspace permission RBAC rules. (#​218, @​Diaphteiros)

v2.0.0

Compare Source

Changelog

🚨 Breaking

[DEVELOPER]
  • The MemberOverrides k8s resource has been removed. The struct in the config which holds the overrides has been renamed from MemberOverridesV2 to MemberOverrides. The structure has not changed. (#​210, @​Diaphteiros)
[OPERATOR]
  • The repository and all resulting artifacts are now named platform-service-project-workspace. (#​214, @​Diaphteiros)
  • The project-workspace-operator can only only be deployed as platform service. The helm chart has been removed and the init and run subcommands now do what previously platformservice init and platformservice run did. (#​210, @​Diaphteiros)
  • The project-workspace-operator does not support pure v1 landscapes anymore. It can still support hybrid landscapes (which offer v1 and v2 in parallel) via its 'v1 support mode', but its defaults always include the v2 resources and it will always check for registered ServiceProvider resources. (#​210, @​Diaphteiros)
  • The run subcommand accepts a --v1 flag, which will include the v1 resources (ManagedControlPlane, ClusterAdmin) in several places. This is just a convenience feature, the same effect can be achieved by adding the v1 resources in the configuration to spec.workspace.deletionBlockingResources and spec.workspace.additionalPermissions. Note that setting the flag requires a non-standard PlatformService manifest, an example can be generated by using task platformservice-v1. (#​210, @​Diaphteiros)

🚀 Features

[OPERATOR]
  • Projects/workspaces which cannot be deleted due to remaining resources are now requeued with an increasing interval instead of every three seconds. This should reduce excessive logging. (#​210, @​Diaphteiros)
[USER]

📚 Documentation

[OPERATOR]

➕ Other

[OPERATOR]

v1.4.0

Compare Source

Changes included in v1.4.0:

Changelog

🚨 Breaking

[OPERATOR]
  • Instead of memberOverridesName, the memberOverrides are now specified in the ProjectWorkspaceConfig's spec directly. (#​196, @​Diaphteiros)

🚀 Features

[OPERATOR]
  • The kind field in a MemberOverride's OverrideResource specification now also accepts Project and Workspace, while it only allowed the lowercase versions of these strings before. In addition, constants for both values have been added. (#​196, @​Diaphteiros)

🐛 Bugfixes

[OPERATOR]
  • The 'member overrides' feature is now better usable for the v2 variant. It does not require any additional resource on the onboarding cluster anymore, instead the configuration is now part of the ProjectWorkspaceConfig resource. (#​196, @​Diaphteiros)
[USER]
  • Fixed a bug which caused the builtin list of resources that block project/workspace deletion not being reflected in the dynamic AccessRequest's permissions. This caused errors when trying to delete a project or workspace, as the controller was lacking permissions. (#​201, @​Diaphteiros)

Configuration

📅 Schedule: (UTC)

  • 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 is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Apr 27, 2026

⚠️ Artifact update problem

Renovate 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:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: go.sum
Command failed: go get -t ./...
go: github.com/openmcp-project/project-workspace-operator/api/v2@v2.0.1: parsing go.mod:
	module declares its path as: github.com/openmcp-project/platform-service-project-workspace/api/v2
	        but was required as: github.com/openmcp-project/project-workspace-operator/api/v2

@renovate renovate Bot force-pushed the renovate/github.com-openmcp-project-project-workspace-operator-api-2.x branch from 7ec748c to 5ae4e35 Compare May 28, 2026 07:10
@renovate renovate Bot force-pushed the renovate/github.com-openmcp-project-project-workspace-operator-api-2.x branch from 5ae4e35 to dd27e03 Compare May 28, 2026 10:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants