Skip to content

[2045] Prevent unwanted compartments from being revealed at node creation#2088

Closed
gcoutable wants to merge 2 commits intogco/cln/reduce-deprecated-usefrom
gco/fix/2045
Closed

[2045] Prevent unwanted compartments from being revealed at node creation#2088
gcoutable wants to merge 2 commits intogco/cln/reduce-deprecated-usefrom
gco/fix/2045

Conversation

@gcoutable
Copy link
Member

@gcoutable gcoutable commented Mar 23, 2026

  • [2045] Prevent unwanted compartments from being revealed at node creation

PLEASE READ ALL ITEMS AND CHECK ONLY RELEVANT CHECKBOXES BELOW

Auto review

  • Have you reviewed this PR? Please do a first quick review, It is very useful to detect typos and missing copyrights, check comments, check your code... The reviewer will thank you for that :)

Project management

  • Has the pull request been added to the relevant milestone?
  • Have the priority: and pr: labels been added to the pull request? (In case of doubt, start with the labels priority: low and pr: to review later)
  • Have the relevant issues been added to the pull request?
  • Have the relevant labels been added to the issues? (area:, type:)
  • Have the relevant issues been added to the same project milestone as the pull request?

Changelog and release notes

  • Has the CHANGELOG.adoc + doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc been updated to reference the relevant issues?
  • Have the relevant API breaks been described in the CHANGELOG.adoc?
  • Are the new / upgraded dependencies mentioned in the relevant section of the CHANGELOG.adoc?
  • In case of a change with a visual impact, are there any screenshots in the doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?
  • In case of a key change, has the change been added to Key highlights section in doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?

Documentation

  • Have you included an update of the documentation in your pull request? Please ask yourself if an update (installation manual, user manual, developer manual...) is needed and add one accordingly.

Tests

  • Is the code properly tested? Any pull request (fix, enhancement or new feature) should come with a test (or several). It could be unit tests, integration tests or cypress tests depending on the context. Only doc and releng pull request do not need for tests.

Signed-off-by: Guillaume Coutable <guillaume.coutable@obeo.fr>
@gcoutable gcoutable added this to the 2026.3.0 milestone Mar 23, 2026
@gcoutable gcoutable changed the base branch from main to gco/cln/reduce-deprecated-use March 23, 2026 10:31
@gcoutable gcoutable linked an issue Mar 23, 2026 that may be closed by this pull request
…tion

Bug: #2045
Signed-off-by: Guillaume Coutable <guillaume.coutable@obeo.fr>
@AxelRICHARD AxelRICHARD force-pushed the gco/cln/reduce-deprecated-use branch from ca26def to dbb8ae1 Compare March 24, 2026 11:03
@AxelRICHARD
Copy link
Member

@gcoutable Can you rebase over cooldown branch please?

@AxelRICHARD AxelRICHARD deleted the branch gco/cln/reduce-deprecated-use March 24, 2026 12:10
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.

Do not reveal parts compartment when create a PartUsage in IV

2 participants