Bump senzing-factory/build-resources/.github/workflows/add-to-project.yaml from 3 to 4

[dependabot]

Bumps senzing-factory/build-resources/.github/workflows/add-to-project.yaml from 3 to 4.

Release notes

Sourced from senzing-factory/build-resources/.github/workflows/add-to-project.yaml's releases.

4.0.0

What's Changed

• #260 make shared workflows generic, misc cleanup by @​kernelsam in senzing-factory/build-resources#261

Full Changelog: senzing-factory/build-resources@v3...4.0.0

3.0.31

What's Changed

• Bump super-linter/super-linter from 8.4.0 to 8.5.0 by @​dependabot[bot] in senzing-factory/build-resources#257
• if the PR's REFRESHED_AT matches main's value, it only passes if that… by @​kernelsam in senzing-factory/build-resources#259

Full Changelog: senzing-factory/build-resources@v3...3.0.31

3.0.30

What's Changed

• Bump super-linter/super-linter from 8.3.1 to 8.3.2 by @​dependabot[bot] in senzing-factory/build-resources#254
• Bump actions/download-artifact from 6 to 7 by @​dependabot[bot] in senzing-factory/build-resources#250
• Bump super-linter/super-linter from 8.3.2 to 8.4.0 by @​dependabot[bot] in senzing-factory/build-resources#255
• Bump actions/upload-artifact from 5 to 6 by @​dependabot[bot] in senzing-factory/build-resources#249
• Fix regex for filtering GitHub workflows by @​kernelsam in senzing-factory/build-resources#256

Full Changelog: senzing-factory/build-resources@v3...3.0.30

3.0.29

What's Changed

• Bump super-linter/super-linter from 8.3.0 to 8.3.1 by @​dependabot[bot] in senzing-factory/build-resources#252
• Remove validation for natural language in workflows by @​kernelsam in senzing-factory/build-resources#253

Full Changelog: senzing-factory/build-resources@v3...3.0.29

3.0.28

What's Changed

• Add Markdown formatting guidelines to PR template by @​kernelsam in senzing-factory/build-resources#244
• Enhance PR review instructions for local and GitHub by @​kernelsam in senzing-factory/build-resources#246
• 247 dockter 1 by @​docktermj in senzing-factory/build-resources#248

New Contributors

• @​docktermj made their first contribution in senzing-factory/build-resources#248

Full Changelog: senzing-factory/build-resources@v3...3.0.28

3.0.27

Full Changelog: senzing-factory/build-resources@v3...3.0.27

3.0.26

Full Changelog: senzing-factory/build-resources@v3...3.0.26

... (truncated)

Changelog

Sourced from senzing-factory/build-resources/.github/workflows/add-to-project.yaml's changelog.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, markdownlint, and this project adheres to Semantic Versioning.

[Unreleased]

• Thing 5
• Thing 4

[1.0.1] - yyyy-mm-dd

Added to 1.0.1

• Thing 3

Fixed in 1.0.1

• Thing 2

[1.0.0] - yyyy-mm-dd

Added to 1.0.0

• Thing 2
• Thing 1

Commits

• 52eb86b bump tags to v4, slack channel override, missing claude settings (#262)
• 08fb769 #260 make shared workflows generic, misc cleanup (#261)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---

Resolves #260
Resolves #262
Resolves #261
Resolves senzing-factory/build-resources#261
Resolves senzing-factory/build-resources#257
Resolves senzing-factory/build-resources#259
Resolves senzing-factory/build-resources#254
Resolves senzing-factory/build-resources#250
Resolves senzing-factory/build-resources#255
Resolves senzing-factory/build-resources#249
Resolves senzing-factory/build-resources#256
Resolves senzing-factory/build-resources#252
Resolves senzing-factory/build-resources#253
Resolves senzing-factory/build-resources#244
Resolves senzing-factory/build-resources#246
Resolves senzing-factory/build-resources#248

[github-actions]

🤖 Claude Code Review

Code Review Analysis

Review Results

Code Quality

✅ Code follows style guide

• This is a GitHub Actions workflow configuration file updating a version reference from @v3 to @v4
• YAML formatting is correct and follows standard conventions
• .github/workflows/add-to-project-garage.yaml:17 - Version bump is properly formatted

✅ No commented-out code

• No commented code present in the diff

✅ Meaningful variable names

• All variable names (SENZING_GITHUB_PROJECT_RW_TOKEN, SENZING_PROJECT_GARAGE, SENZING_GITHUB_ACCOUNT_NAME) are descriptive and follow conventions

✅ DRY principle followed

• Single line change, no duplication introduced

✅ No defects identified

• Version bump from v3 to v4 of the reusable workflow reference
• No logic errors, edge cases, or security vulnerabilities introduced
• This is a standard dependency version update

✅ Project memory consideration

• No .claude/CLAUDE.md file exists in the repository to consider

Testing

⚠️ Testing considerations

• .github/workflows/add-to-project-garage.yaml:17 - This is a workflow dependency update
• Testing would typically be done by the maintainers of senzing-factory/build-resources repository
• Cannot assess test coverage for the upstream workflow changes
• Recommend verifying that the workflow runs successfully after merge

Documentation

❌ CHANGELOG.md not updated

• No CHANGELOG.md update included in this PR
• Version bumps of dependencies should typically be documented
• Recommend adding an entry describing the update from v3 to v4

⚠️ README update assessment

• No README changes needed for this type of internal workflow update
• However, if v4 introduces breaking changes or new features, documentation may be needed

✅ Markdown formatting

• No markdown files modified in this diff

Security

✅ No hardcoded credentials

• Secrets and variables properly referenced using GitHub Actions context (${{ secrets.X }}, ${{ vars.X }})

✅ No sensitive data in logs

• No logging changes introduced

✅ No license files checked in

• No .lic files or AQAAAD strings present in the diff

✅ Proper secret handling

• .github/workflows/add-to-project-garage.yaml:16 - SENZING_GITHUB_PROJECT_RW_TOKEN correctly passed as a secret

Summary

Approval Status: ✅ APPROVED with minor documentation recommendation

This is a clean version bump of a reusable workflow dependency. The change is minimal and follows proper GitHub Actions conventions.

Recommendation: Add a CHANGELOG.md entry documenting this workflow version update to maintain a complete change history.

Risk Level: Low - Standard dependency update with no breaking changes to this workflow file's interface.

Automated code review analyzing defects and coding standards

[github-actions]

🤖 Claude Code Review

Automated Code Review

Code Quality

✅ Code follows style guide

• The change is a simple version bump in a GitHub Actions workflow file
• YAML formatting is correct and consistent
• File path: .github/workflows/add-to-project-garage.yaml:17

✅ No commented-out code

• No commented code present in the diff

✅ Meaningful variable names

• Not applicable - this is a version reference update, no variables changed

✅ DRY principle followed

• Not applicable - single line version bump

✅ Identify Defects

• No bugs or logic errors detected
• This is a standard workflow version upgrade from v3 to v4
• Recommendation: Verify that the v4 tag exists in the senzing-factory/build-resources repository and that the workflow is compatible with current configuration
• Consideration: Ensure the changelog or release notes for v4 don't introduce breaking changes that would affect this workflow's behavior

⚠️ Project Memory Configuration

• No .claude/CLAUDE.md file detected in the repository to evaluate against

Testing

❌ Unit tests for new functions

• Not applicable - workflow configuration change doesn't require unit tests
• Note: This type of change should be validated by testing the workflow execution

❌ Integration tests for new endpoints

• Not applicable - no endpoints modified

❌ Edge cases covered

• Not applicable for workflow version bump

❌ Test coverage > 80%

• Not applicable - infrastructure/CI configuration change

Recommendation: Test this workflow change in a safe environment (e.g., test PR) to ensure v4 works as expected before widespread adoption.

Documentation

⚠️ Readme updated if needed

• For a workflow version bump, README update is typically not required unless the workflow behavior changes significantly
• Action needed: Review the v4 release notes to determine if documentation updates are needed

✅ API docs updated

• Not applicable - no API changes

✅ Inline comments for complex logic

• Not applicable - simple version reference

⚠️ CHANGELOG.md updated

• No CHANGELOG.md changes detected in this diff
• Recommendation: Consider adding an entry documenting the upgrade to v4 and why it was needed (new features, bug fixes, etc.)

✅ Markdown formatting

• Not applicable - YAML file only in this diff

Security

✅ No hardcoded credentials

• No credentials in the change
• Proper use of secrets: ${{ secrets.SENZING_GITHUB_PROJECT_RW_TOKEN }}

✅ Input validation implemented

• Not applicable - workflow configuration

✅ Proper error handling

• Delegated to the called workflow

✅ No sensitive data in logs

• No changes affecting logging

✅ No license files or AQAAAD strings

• No license files detected in this diff

---

Summary

Overall Assessment: ✅ APPROVED with recommendations

This is a straightforward version bump from v3 to v4 of a reusable workflow. The change is clean and follows proper practices.

Required Actions:

None - the change is safe to merge

Recommended Actions:

1. Verify the v4 tag exists and review its release notes/changelog for any breaking changes
2. Consider updating CHANGELOG.md to document this infrastructure change
3. Test the workflow execution after merge to ensure v4 behaves as expected

Files Reviewed:

• .github/workflows/add-to-project-garage.yaml:17 - Version bump only

---

Automated code review analyzing defects and coding standards

[github-actions]

🤖 Claude Code Review

Code Review Analysis

Code Quality

✅ Code follows our style guide

• The change is a simple version bump in a GitHub Actions workflow file
• Follows YAML formatting standards
• No code style issues present

✅ No commented-out code

• No commented code found in this change

✅ Meaningful variable names

• Not applicable - this is a version reference change only

✅ DRY principle followed

• Not applicable - no code duplication possible in this single-line change

✅ Identify Defects

• No bugs, logic errors, or security vulnerabilities detected
• The change updates the reusable workflow reference from @v3 to @v4
• This is a standard dependency update pattern in GitHub Actions
• No edge cases or potential crashes

✅ Project memory configuration

• No ./.claude/CLAUDE.md file found in the repository to consider

Testing

⚠️ Testing considerations

• Unit tests: Not applicable for workflow version bumps
• Integration tests: Not applicable
• Edge cases: Not applicable
• Test coverage: Not applicable

Note: While automated tests don't apply here, this change should be verified by:

• Ensuring the @v4 version of the reusable workflow exists at senzing-factory/build-resources
• Confirming the workflow runs successfully after the update
• Reviewing the changelog/release notes for the @v4 version to understand what changed

Documentation

✅ Readme updated if needed

• Not required - this is an internal workflow dependency update

✅ API docs updated

• Not applicable

✅ Inline comments for complex logic

• Not applicable - the change is self-explanatory

❌ CHANGELOG.md updated

• Location: ./CHANGELOG.md (if exists at repository root)
• This version bump should be documented, especially if there are breaking changes or new features in the @v4 reusable workflow
• Recommendation: Add an entry like "Updated add-to-project workflow to v4"

✅ Markdown files formatting

• No markdown files modified in this PR

Security

✅ No hardcoded credentials

• Secrets are properly referenced via ${{ secrets.* }}
• Variables are properly referenced via ${{ vars.* }}

✅ Input validation implemented

• Not applicable to this change

✅ Proper error handling

• Not applicable to this change

✅ No sensitive data in logs

• No logging changes in this PR

✅ No license files or AQAAAD strings

• No .lic files or suspicious license strings detected

---

Summary

Overall Assessment: ✅ APPROVED with minor documentation suggestion

This is a clean, straightforward dependency update that bumps a reusable GitHub Actions workflow from v3 to v4. The change is minimal and low-risk.

Action Items:

1. 📝 Consider adding a CHANGELOG.md entry documenting this workflow version update
2. ✓ Verify the @v4 version of the reusable workflow exists and is compatible
3. ✓ Test the workflow runs successfully after merge

No blocking issues found.

Automated code review analyzing defects and coding standards

[github-actions]

🤖 Claude Code Review

Automated Code Review

Code Quality

✅ Code follows style guide

The change is a simple version bump in a GitHub Actions workflow file. The formatting and structure follow standard YAML conventions and GitHub Actions best practices.

✅ No commented-out code

No commented-out code present in this change.

✅ Meaningful variable names

Not applicable - this is a workflow version reference update, not variable naming.

✅ DRY principle followed

Not applicable - this is a single version reference update.

✅ Identify Defects

No defects identified. The change updates the reusable workflow reference from v3 to v4. This is a standard version bump pattern. However, considerations:

• File: .github/workflows/add-to-project-garage.yaml:17
• Ensure the v4 version of the reusable workflow at senzing-factory/build-resources is compatible with the existing inputs and secrets being passed
• The project-number, org, and SENZING_GITHUB_PROJECT_RW_TOKEN should be compatible with v4 (this requires verification against the upstream workflow)

✅ Project memory configuration

No .claude/CLAUDE.md file was found in the repository context, so this check is not applicable.

Testing

⚠️ Unit tests for new functions

Not applicable - this is a workflow version bump, not new function code. However, this change should be tested by:

• Verifying the workflow runs successfully with v4
• Confirming issues are still added to the correct project

❌ Integration tests for new endpoints

Not applicable for workflow configuration.

⚠️ Edge cases covered

The edge case to consider: What happens if v4 introduces breaking changes? Recommendation:

• Review the changelog/release notes for senzing-factory/build-resources/.github/workflows/add-to-project.yaml@v4
• Test in a non-production scenario first if possible

❌ Test coverage > 80%

Not applicable for YAML workflow files.

Documentation

⚠️ Readme updated if needed

Cannot determine without seeing the README. If the README documents workflow versions or build processes, it may need updating.

❌ API docs updated

Not applicable - no API changes.

❌ Inline comments for complex logic

Not applicable - this is a straightforward version reference change.

❌ CHANGELOG.md updated

File: CHANGELOG.md (expected location)
The CHANGELOG should be updated to reflect this dependency version bump, especially if v4 introduces new features or breaking changes that affect behavior.

✅ Markdown files follow CommonMark

Not applicable - no markdown files modified in this diff.

Security

✅ No hardcoded credentials

No credentials hardcoded. The secret SENZING_GITHUB_PROJECT_RW_TOKEN is properly referenced from GitHub Secrets.

✅ Input validation implemented

Not applicable - GitHub Actions handles workflow input validation.

✅ Proper error handling

Error handling is delegated to the reusable workflow being called.

✅ No sensitive data in logs

No sensitive data exposed in this configuration change.

✅ No license files checked in

No .lic files or AQAAAD strings present in this diff.

---

Summary

Overall Assessment: ✅ APPROVED with minor recommendations

This is a low-risk change that updates a reusable workflow version reference. The change itself is clean and follows best practices.

Recommendations:

1. Before merging: Verify that v4 of the reusable workflow is compatible with the current inputs (project-number, org) and required permissions.
2. Post-merge: Monitor the first workflow run to ensure successful execution.
3. Optional: Update CHANGELOG.md to document this dependency version bump if your team tracks such changes.

Critical Issues: None
Blocking Issues: None
Warnings: See edge case testing recommendation above

Automated code review analyzing defects and coding standards