Skip to content

Conversation

@shikanime
Copy link
Contributor

@shikanime shikanime commented Feb 6, 2026

@github-actions
Copy link
Contributor

github-actions bot commented Feb 6, 2026

🤖 Hey !

The @cpn-console/hooks (v4.0.0) package already exists on npm but the source code has changed, you should consider updating the package version.

The version update warning should be ignored in the case of modifications that do not affect the code once it has been built, such as code formatting, etc...

@github-actions
Copy link
Contributor

github-actions bot commented Feb 6, 2026

🤖 Hey !

The @cpn-console/keycloak-plugin (v2.1.0) package already exists on npm but the source code has changed, you should consider updating the package version.

The version update warning should be ignored in the case of modifications that do not affect the code once it has been built, such as code formatting, etc...

@github-actions
Copy link
Contributor

github-actions bot commented Feb 6, 2026

🤖 Hey !

The @cpn-console/sonarqube-plugin (v2.0.5) package already exists on npm but the source code has changed, you should consider updating the package version.

The version update warning should be ignored in the case of modifications that do not affect the code once it has been built, such as code formatting, etc...

@github-actions
Copy link
Contributor

github-actions bot commented Feb 6, 2026

🤖 Hey !

The @cpn-console/shared (v1.3.0) package already exists on npm but the source code has changed, you should consider updating the package version.

The version update warning should be ignored in the case of modifications that do not affect the code once it has been built, such as code formatting, etc...

@github-actions
Copy link
Contributor

github-actions bot commented Feb 6, 2026

🤖 Hey !

The @cpn-console/gitlab-plugin (v3.3.1) package already exists on npm but the source code has changed, you should consider updating the package version.

The version update warning should be ignored in the case of modifications that do not affect the code once it has been built, such as code formatting, etc...

@shikanime shikanime changed the title feat(sonarrqube): make admin group path configurable though console feat(sonarqube): make admin group path configurable though console Feb 6, 2026
@shikanime shikanime marked this pull request as draft February 6, 2026 15:28
@github-actions github-actions bot added the built label Feb 6, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Feb 6, 2026

🤖 Hey !

The security scan report for the current pull request is available here.

.filter((g): g is string => !!g)

// Sync Roles
for (const roleGroup of allRoleGroups) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: Il va nous falloir quelques tests auto pour documenter/valider ces invariants.

@cloud-pi-native-sonarqube
Copy link

@shikanime shikanime marked this pull request as draft February 10, 2026 13:28
@shikanime shikanime force-pushed the pr1905 branch 4 times, most recently from d2b890b to 2fc246e Compare February 11, 2026 09:11
@shikanime shikanime force-pushed the pr1905 branch 2 times, most recently from 2df3a80 to 02c0507 Compare February 11, 2026 09:24
For some reasons, the config is never passed down to the plugins hooks. Apparently the config is provided via the adminPlugin table of the database but is empty most of the time so for the moment let's just add default and fix the problem properly later.

Signed-off-by: William Phetsinorath <[email protected]>
We don't want drift to be an option in the future, so we'll keep the purge option as an admin only.

Signed-off-by: William Phetsinorath <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants