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

feat(gitea)!: use Bearer instead of token for auth #28308

Merged
merged 4 commits into from
Apr 13, 2024
Merged

feat(gitea)!: use Bearer instead of token for auth #28308

merged 4 commits into from
Apr 13, 2024

Conversation

viceice
Copy link
Member

@viceice viceice commented Apr 10, 2024

Changes

Gitea supports Bearer als alternate to token since v1.8.0

Context

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

  • Code inspection only, or
  • Newly added/modified unit tests, or
  • No unit tests but ran on a real repository, or
  • Both unit tests + ran on a real repository

rarkins and others added 2 commits March 27, 2024 04:51
@rarkins
fix(config): globalExtends merge default (#28145)
d9ba74d 
Previously, config from globalExtends was incorrectly merged _after_ other global config. This meant for example that packageRules in a config.js could not override packageRules from within globalExtends, because they were applied after. Now, globalExtends content will be merged first, and remaining global config merged second.

Fixes #28131

BREAKING CHANGE: order of globalExtends resolution is changed so that it is applied first and remaining global config takes precedence.
@secustor @viceice
feat(manager/pep621): allow auto grouping of dependencies in differen…
05dcbc8 
…t groups (#28193)

Co-authored-by: Michael Kriese <[email protected]>
@viceice viceice added the breaking Breaking change, requires major version bump label Apr 10, 2024
@viceice viceice changed the base branch from main to v38 April 10, 2024 08:41
@viceice viceice mentioned this pull request Apr 10, 2024
Closed
23 tasks
@viceice viceice requested a review from rarkins April 10, 2024 10:20
@rarkins rarkins changed the title feat(gitea): use Bearer instead of token for auth feat(gitea)!: use Bearer instead of token for auth Apr 13, 2024
@rarkins rarkins merged commit 2dc70ac into v38 Apr 13, 2024
34 checks passed
@rarkins rarkins deleted the feat/gitea/bearer branch April 13, 2024 09:06
rarkins added a commit that referenced this pull request Apr 14, 2024
@viceice @rarkins @secustor
feat(gitea)!: use Bearer instead of token for auth (#28308)
e4fd0e2 
Co-authored-by: Rhys Arkins <[email protected]>
Co-authored-by: Sebastian Poxhofer <[email protected]>
rarkins added a commit that referenced this pull request Apr 14, 2024
@viceice @rarkins @secustor
feat(gitea)!: use Bearer instead of token for auth (#28308)
a406aa7 
Co-authored-by: Rhys Arkins <[email protected]>
Co-authored-by: Sebastian Poxhofer <[email protected]>
rarkins added a commit that referenced this pull request Apr 14, 2024
@viceice @rarkins @secustor
feat(gitea)!: use Bearer instead of token for auth (#28308)
fdc9cbb 
Co-authored-by: Rhys Arkins <[email protected]>
Co-authored-by: Sebastian Poxhofer <[email protected]>
rarkins pushed a commit that referenced this pull request Apr 14, 2024
@viceice @rarkins
feat(gitea)!: use Bearer instead of token for auth (#28308)
6717725 
Previous Gitea implementation used non-standard “token” auth instead of “Bearer”. Gitea supports Bearer al alternate to token since v1.8.0, so it’s safe to make this change now.

BREAKING CHANGE: Gitea platfor authentication will now be done using Bearer auth instead of token auth.
rarkins pushed a commit that referenced this pull request Apr 14, 2024
@viceice @rarkins
feat(gitea)!: use Bearer instead of token for auth (#28308)
f858742 
Previous Gitea implementation used non-standard “token” auth instead of “Bearer”. Gitea supports Bearer al alternate to token since v1.8.0, so it’s safe to make this change now.

BREAKING CHANGE: Gitea platfor authentication will now be done using Bearer auth instead of token auth.
rarkins pushed a commit that referenced this pull request Apr 20, 2024
@viceice @rarkins
feat(gitea)!: use Bearer instead of token for auth (#28308)
37a36d2 
Previous Gitea implementation used non-standard “token” auth instead of “Bearer”. Gitea supports Bearer al alternate to token since v1.8.0, so it’s safe to make this change now.

BREAKING CHANGE: Gitea platfor authentication will now be done using Bearer auth instead of token auth.
rarkins pushed a commit that referenced this pull request Apr 21, 2024
@viceice @rarkins
feat(gitea)!: use Bearer instead of token for auth (#28308)
a041501 
Previous Gitea implementation used non-standard “token” auth instead of “Bearer”. Gitea supports Bearer al alternate to token since v1.8.0, so it’s safe to make this change now.

BREAKING CHANGE: Gitea platfor authentication will now be done using Bearer auth instead of token auth.
rarkins pushed a commit that referenced this pull request Apr 21, 2024
@viceice @rarkins
feat(gitea)!: use Bearer instead of token for auth (#28308)
784174a 
Previous Gitea implementation used non-standard “token” auth instead of “Bearer”. Gitea supports Bearer al alternate to token since v1.8.0, so it’s safe to make this change now.

BREAKING CHANGE: Gitea platfor authentication will now be done using Bearer auth instead of token auth.
rarkins pushed a commit that referenced this pull request Apr 22, 2024
@viceice @rarkins
feat(gitea)!: use Bearer instead of token for auth (#28308)
af9519b 
Previous Gitea implementation used non-standard “token” auth instead of “Bearer”. Gitea supports Bearer al alternate to token since v1.8.0, so it’s safe to make this change now.

BREAKING CHANGE: Gitea platfor authentication will now be done using Bearer auth instead of token auth.
rarkins pushed a commit that referenced this pull request Apr 26, 2024
@viceice @rarkins
feat(gitea)!: use Bearer instead of token for auth (#28308)
5227276 
Previous Gitea implementation used non-standard “token” auth instead of “Bearer”. Gitea supports Bearer al alternate to token since v1.8.0, so it’s safe to make this change now.

BREAKING CHANGE: Gitea platfor authentication will now be done using Bearer auth instead of token auth.
rarkins pushed a commit that referenced this pull request Apr 29, 2024
@viceice @rarkins
feat(gitea)!: use Bearer instead of token for auth (#28308)
b739aa0 
Previous Gitea implementation used non-standard “token” auth instead of “Bearer”. Gitea supports Bearer al alternate to token since v1.8.0, so it’s safe to make this change now.

BREAKING CHANGE: Gitea platfor authentication will now be done using Bearer auth instead of token auth.
rarkins pushed a commit that referenced this pull request May 3, 2024
@viceice @rarkins
feat(gitea)!: use Bearer instead of token for auth (#28308)
ddab94b 
Previous Gitea implementation used non-standard “token” auth instead of “Bearer”. Gitea supports Bearer al alternate to token since v1.8.0, so it’s safe to make this change now.

BREAKING CHANGE: Gitea platfor authentication will now be done using Bearer auth instead of token auth.
rarkins pushed a commit that referenced this pull request May 4, 2024
@viceice @rarkins
feat(gitea)!: use Bearer instead of token for auth (#28308)
7604a84 
Previous Gitea implementation used non-standard “token” auth instead of “Bearer”. Gitea supports Bearer al alternate to token since v1.8.0, so it’s safe to make this change now.

BREAKING CHANGE: Gitea platfor authentication will now be done using Bearer auth instead of token auth.
rarkins pushed a commit that referenced this pull request May 5, 2024
@viceice @rarkins
feat(gitea)!: use Bearer instead of token for auth (#28308)
dfcc4cc 
Previous Gitea implementation used non-standard “token” auth instead of “Bearer”. Gitea supports Bearer al alternate to token since v1.8.0, so it’s safe to make this change now.

BREAKING CHANGE: Gitea platfor authentication will now be done using Bearer auth instead of token auth.
rarkins pushed a commit that referenced this pull request May 6, 2024
@viceice @rarkins
feat(gitea)!: use Bearer instead of token for auth (#28308)
8654392 
Previous Gitea implementation used non-standard “token” auth instead of “Bearer”. Gitea supports Bearer al alternate to token since v1.8.0, so it’s safe to make this change now.

BREAKING CHANGE: Gitea platfor authentication will now be done using Bearer auth instead of token auth.
rarkins pushed a commit that referenced this pull request May 11, 2024
@viceice @rarkins
feat(gitea)!: use Bearer instead of token for auth (#28308)
b05ac26 
Previous Gitea implementation used non-standard “token” auth instead of “Bearer”. Gitea supports Bearer al alternate to token since v1.8.0, so it’s safe to make this change now.

BREAKING CHANGE: Gitea platfor authentication will now be done using Bearer auth instead of token auth.
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@rarkins rarkins rarkins approved these changes

Assignees
No one assigned
Labels
breaking Breaking change, requires major version bump
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@viceice @rarkins @secustor