Skip to content

fix: configure unique component tags for monorepo releases#11

Merged
chrislyons-dev merged 6 commits intomainfrom
cosmetic-updates
Oct 31, 2025
Merged

fix: configure unique component tags for monorepo releases#11
chrislyons-dev merged 6 commits intomainfrom
cosmetic-updates

Conversation

@chrislyons-dev
Copy link
Copy Markdown
Owner

  • Add include-component-in-tag to release-please config
  • Set unique component names for TypeScript and Python packages
  • Update workflow outputs to use component-based variable names
  • Add manual publish workflow for retroactive publishing

This fixes the issue where both packages shared the same Git tag
(flarelette-jwt-v1.8.1), causing only one release to be created and
the PyPI publish job to be skipped.

Future releases will use tags like:

  • flarelette-jwt-ts-v1.8.1
  • flarelette-jwt-py-v1.8.1

🤖 Generated with Claude Code

Co-Authored-By: Claude noreply@anthropic.com"
Commit workflow fixes

cjlyons and others added 6 commits October 31, 2025 10:46
- Add include-component-in-tag to release-please config
- Set unique component names for TypeScript and Python packages
- Update workflow outputs to use component-based variable names
- Add manual publish workflow for retroactive publishing

This fixes the issue where both packages shared the same Git tag
(flarelette-jwt-v1.8.1), causing only one release to be created and
the PyPI publish job to be skipped.

Future releases will use tags like:
- flarelette-jwt-ts-v1.8.1
- flarelette-jwt-py-v1.8.1

Written-by: Chris Lyons
Co-Authored-By: Claude <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown
Contributor

Dependency Review

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

OpenSSF Scorecard

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

Scanned Files

  • .github/workflows/manual-publish.yml

@chrislyons-dev chrislyons-dev merged commit 6e57f26 into main Oct 31, 2025
29 checks passed
@github-actions github-actions Bot mentioned this pull request Oct 31, 2025
@chrislyons-dev chrislyons-dev deleted the cosmetic-updates branch October 31, 2025 22:09
This was referenced Nov 1, 2025
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.

2 participants