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

ci(test): test release process 🧪 #562

Closed
wants to merge 0 commits into from
Closed

ci(test): test release process 🧪 #562

wants to merge 0 commits into from

Conversation

JamieSlome
Copy link
Member

Testing implementations and configuration for #557

@JamieSlome JamieSlome added the dependencies Pull requests that update a dependency file label May 13, 2024
@JamieSlome JamieSlome self-assigned this May 13, 2024
@JamieSlome JamieSlome linked an issue May 13, 2024 that may be closed by this pull request
Automatically increment version in package.json on new release 📦 #557
Open
@github-actions GitHub Actions
Copy link

github-actions bot commented May 13, 2024 •
edited

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

PackageVersionScoreDetails
actions/actions/checkout 8459bc0 🟢 7.6
Details
CheckScoreReason
Code-Review🟢 10all changesets reviewed
Maintained🟢 1021 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
License🟢 10license file detected
Signed-Releases⚠️ -1no releases found
Branch-Protection⚠️ -1internal error: error during branchesHandler.setup: internal error: githubv4.Query: Resource not accessible by integration
Binary-Artifacts🟢 10no binaries found in the repo
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Fuzzing⚠️ 0project is not fuzzed
Packaging🟢 10packaging workflow detected
Security-Policy🟢 9security policy file detected
SAST🟢 10SAST tool is run on all commits
Vulnerabilities🟢 100 existing vulnerabilities detected
Pinned-Dependencies🟢 4dependency not pinned by hash detected -- score normalized to 4
actions/actions/setup-node c2ac33f 🟢 5.6
Details
CheckScoreReason
Code-Review🟢 10all changesets reviewed
Maintained⚠️ 12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
License🟢 10license file detected
Branch-Protection⚠️ -1internal error: error during branchesHandler.setup: internal error: githubv4.Query: Resource not accessible by integration
Signed-Releases⚠️ -1no releases found
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Packaging⚠️ -1packaging workflow not detected
Binary-Artifacts🟢 9binaries present in source code
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Fuzzing⚠️ 0project is not fuzzed
Security-Policy🟢 9security policy file detected
SAST🟢 10SAST tool is run on all commits
Vulnerabilities🟢 55 existing vulnerabilities detected
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
actions/release-drafter/release-drafter 6.*.* 🟢 3.4
Details
CheckScoreReason
Code-Review🟢 5Found 13/24 approved changesets -- score normalized to 5
Maintained🟢 31 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 3
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
License🟢 10license file detected
Signed-Releases⚠️ -1no releases found
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Packaging⚠️ -1packaging workflow not detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Binary-Artifacts🟢 10no binaries found in the repo
Security-Policy⚠️ 0security policy file not detected
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
Fuzzing⚠️ 0project is not fuzzed
Branch-Protection⚠️ 0branch protection not enabled on development/release branches
Pinned-Dependencies⚠️ 2dependency not pinned by hash detected -- score normalized to 2
Vulnerabilities⚠️ 013 existing vulnerabilities detected

Scanned Manifest Files

.github/workflows/release.yml

@netlify Netlify
Copy link

netlify bot commented May 13, 2024 •
edited

✅ Deploy Preview for endearing-brigadeiros-63f9d0 canceled.

Name Link
🔨 Latest commit eb7c88e
🔍 Latest deploy log https://app.netlify.com/sites/endearing-brigadeiros-63f9d0/deploys/664213b70d94c60008f6d0f1

@JamieSlome JamieSlome changed the title Test release process 🧪 ci(test): test release process 🧪 May 13, 2024
@codecov Codecov
Copy link

codecov bot commented May 13, 2024 •
edited

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 56.96%. Comparing base (eb7c88e) to head (7e0d99c).

Additional details and impacted files 
@@           Coverage Diff           @@
##             main     #562   +/-   ##
=======================================
  Coverage   56.96%   56.96%           
=======================================
  Files          46       46           
  Lines        1566     1566           
=======================================
  Hits          892      892           
  Misses        674      674

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@JamieSlome JamieSlome closed this May 13, 2024
@JamieSlome JamieSlome force-pushed the 557-automatically-increment-version-in-packagejson-on-new-release branch from 7e0d99c to eb7c88e Compare May 13, 2024 13:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@JamieSlome JamieSlome

Labels
automation dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Automatically increment version in package.json on new release 📦
1 participant
@JamieSlome