Skip to content

Conversation

@NicolasMarlier
Copy link

No description provided.

@NicolasMarlier NicolasMarlier changed the title Nma/v1 4 1 Version 1.4.1 Adding license check Dec 16, 2025
@NicolasMarlier NicolasMarlier changed the base branch from nma/v1-4-0 to master December 16, 2025 16:15
Comment on lines +36 to +41
- - :approve
- Pennylane
- :why: Our own software
- - :approve
- pennylane
- :why: Our own software
Copy link

Choose a reason for hiding this comment

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

why putting it twice?

Suggested change
- - :approve
- Pennylane
- :why: Our own software
- - :approve
- pennylane
- :why: Our own software
- - :approve
- Pennylane
- :why: Our own software
- - :approve
- pennylane
- :why: Our own software

Copy link

Choose a reason for hiding this comment

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

ah case sensitive?
I'm not sure I get where this is used

Comment on lines +52 to +63
- - :approve
- sidekiq
- :why: We have purchased a commercial license
- - :approve
- sidekiq-pro
- :why: We have purchased a commercial license
- - :approve
- hexapdf
- :why: We have purchased a commercial license
- - :approve
- fintecture
- :why: Covered by our commercial relationship
Copy link

Choose a reason for hiding this comment

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

we don't really have this in this repo, no?

Copy link

@victorps-pl victorps-pl Dec 16, 2025

Choose a reason for hiding this comment

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

I think it's because the file has been copy-pasted from jeancaisse. We can limit this file to line 35 because below that line are the exceptions for dependencies that are authorized on a case-by-case basis (or we can also keep it as is).

Copy link

@gterral gterral left a comment

Choose a reason for hiding this comment

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

I would clean the file to only contains what's relevant to this repo.

Otherwise I would use a github action to sync this file with the one in jeancaisse

@victorps-pl
Copy link

Hello @NicolasMarlier @ccfz , could we merge this PR, so that we can close the non-conformity? 🙏

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.

4 participants