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.

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

Fix golangci and update versions #76

Merged
merged 3 commits into from
Dec 15, 2024
Merged

Conversation

shibumi
Copy link
Collaborator

@shibumi shibumi commented Nov 29, 2024

We have to unblock development by fixing Github Actions. In this PR, I changed the following:

  1. Pin the test-suite to an older version to avoid npm test failures.
  2. Remove the deprecated linters
  3. Update all linter and OS versions.

@shibumi shibumi force-pushed the fix-ci branch 2 times, most recently from 3bacf5c to 16884d7 Compare November 29, 2024 12:01
@shibumi
Copy link
Collaborator Author

shibumi commented Nov 29, 2024

package-url/purl-spec@c5681ae introduced breakage for our Go implementation or it's something we have to fix in this project to comply with the spec.

@shibumi shibumi force-pushed the fix-ci branch 4 times, most recently from fbad0e2 to e791fd5 Compare November 29, 2024 12:12
@shibumi
Copy link
Collaborator Author

shibumi commented Nov 29, 2024

@sschuberth Can you approve this PR? It fixes the broken golangci and unblocks: #73

Also, I had to pin the test suite file. Looks like the upstream spec changed OR the packageurl-go version has a spec-drift.
We shoudl fix this ASAP and maybe create a trigger that automatically tests the go suite when a new commit hits the spec repository (either time or event based.. I have some ideas there).

@sschuberth
Copy link
Member

sschuberth commented Nov 29, 2024

@sschuberth Can you approve this PR? It fixes the broken golangci and unblocks: #73

Sorry @shibumi, I was asked by @pombredanne to not do any "drive by" reviews anymore. As I'm unsure whether that only applies to the purl-spec project itself, or also to projects for implementations like this, I'll refrain from a review / approval until this is clarified.

@shibumi
Copy link
Collaborator Author

shibumi commented Nov 29, 2024

@sschuberth no problem :)

@pombredanne do you know someone else who would be willing to maintain this project together with me? I need someone who can review PRs

@shibumi
Copy link
Collaborator Author

shibumi commented Dec 8, 2024

@sschuberth I am sure that @pombredanne only meant the specification repository, because that one is VERY important (lot's of projects are depending on it and it's our source of truth).

I really see no problem in approving this PR, here :)

Especially, because @pombredanne seems to be very inactive :/

@stevespringett, @johnmhoran, @iamwillbar, @jkowalleck, sorry for CC'ing you all. Can maybe one of you approve this PR here or can you appoint a second owner for this repository? Currently, all PRs are blocked and we should really fix these CI bugs ASAP.

If you need a good candidate, I can maybe find someone from the open source software supply chain security community.

The newest test-suite have new npm tests that were not yet implemented
in packageurl-go. We will have to add the missing implementation first.

This commit attempts to unblock all CI runs and unblock development.
Certain linters got deprecated in newer golangci-lint versions.
We have to remove those linters from the list to avoid a blocking
linter.
This commit updates several versions in our CI file.
@coveralls
Copy link

Pull Request Test Coverage Report for Build 12339359460

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 86.942%

Totals Coverage Status
Change from base Build 8136782021: 0.0%
Covered Lines: 253
Relevant Lines: 291

💛 - Coveralls

2 similar comments
@coveralls
Copy link

Pull Request Test Coverage Report for Build 12339359460

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 86.942%

Totals Coverage Status
Change from base Build 8136782021: 0.0%
Covered Lines: 253
Relevant Lines: 291

💛 - Coveralls

@coveralls
Copy link

Pull Request Test Coverage Report for Build 12339359460

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 86.942%

Totals Coverage Status
Change from base Build 8136782021: 0.0%
Covered Lines: 253
Relevant Lines: 291

💛 - Coveralls

@shibumi
Copy link
Collaborator Author

shibumi commented Dec 15, 2024

@sschuberth or @jkowalleck feel free to give it another review :)

@sschuberth sschuberth merged commit 1f15199 into package-url:master Dec 15, 2024
2 checks passed
@shibumi shibumi deleted the fix-ci branch December 15, 2024 16:03
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.

3 participants