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.

Sign up for GitHub

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

Jump to bottom

[15.0][MIG] base_rest_auth_jwt: Migration to 15.0 #237

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

[15.0][MIG] base_rest_auth_jwt: Migration to 15.0 #237

wants to merge 1 commit into from

Conversation

yankinmax
Copy link
Contributor

@yankinmax yankinmax commented Dec 15, 2021 •
edited by simahawk
Loading

@yankinmax
Copy link
Contributor Author

@lmignon should we ignore License issue on pre-commit?

base_rest_auth_jwt (LGPL-3) depends on auth_jwt (AGPL-3)
Error: Process completed with exit code 1.

@lmignon
Copy link
Contributor

lmignon commented Dec 15, 2021

@yankinmax No it should not be ignored. We would relicence auth_jwt under LGPL.

@yankinmax yankinmax force-pushed the 15.0-mig-base_rest_auth_jwt branch from c695ba0 to 91217fd Compare December 15, 2021 16:22
@yankinmax yankinmax force-pushed the 15.0-mig-base_rest_auth_jwt branch from 91217fd to ce71c82 Compare December 15, 2021 16:29
@lmignon lmignon mentioned this pull request Dec 16, 2021
Closed
10 tasks
@lmignon
Copy link
Contributor

lmignon commented Jan 25, 2022 •
edited
Loading

@yankinmax Can you rebase your PR? FYI auth_jwt has been re-licensed in V14 OCA/server-auth#319

@yankinmax
Copy link
Contributor Author

@lmignon yes I know about the relicense, I did that PR 😃
But, here I'm waiting for OCA/server-auth#316
If you can help to solve the issue it would be great. Thanks in advance.

@github-actions
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label May 29, 2022
@github-actions github-actions bot closed this Jul 3, 2022
@simahawk simahawk reopened this Oct 20, 2022
@simahawk simahawk added no stale Use this label to prevent the automated stale action from closing this PR/Issue. and removed stale PR/Issue without recent activity, it'll be soon closed automatically. labels Oct 20, 2022
@simahawk
Copy link
Contributor

@SilvioC2C can you have a look here? 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
no stale Use this label to prevent the automated stale action from closing this PR/Issue.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@yankinmax @lmignon @simahawk