chore: update master to main references in docs and scripts

[sayaliM0412]

Summary

• Update master to main in references that point to Liquibase-owned repos (build-logic, liquibase-pro), all of which default to main
• Fix CLAUDE.md nightly description: actual workflow uses main-SNAPSHOT, not master-SNAPSHOT
• Fix README.md build_logic_ref default and the ref: example so they match build-logic's actual default branch
• Update SonarSource sonar-scanning-examples doc link (repo migrated to main)
• Drop the stale "master" example from subtree-sync.yml input description

External fossa-cli URLs were intentionally left on master because that repo still uses master as its default branch.

Files changed

• CLAUDE.md: master-SNAPSHOT to main-SNAPSHOT
• README.md: build_logic_ref default, ref: master example, sonar-scanning-examples link
• .github/workflows/subtree-sync.yml: input description
• scripts/vulnerability-scanning/diff-new-cves.sh: comment + log message referring to liquibase-pro

Test plan

• Verify nothing in the consuming workflows depends on the literal string master in these locations (all changes are in docs/comments/log messages, not in executable workflow logic)
• Confirm SonarSource sonar-scanning-examples main link resolves
• Confirm consuming repos that pin build_logic_ref are not relying on the documented default (they pass an explicit value)

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com

[coderabbitai]

Warning

Rate limit exceeded

@sayaliM0412 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 56 minutes and 51 seconds before requesting another review.

To continue reviewing without waiting, purchase usage credits in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1c0360e1-637b-467a-919a-e608854a79f9

📥 Commits

Reviewing files that changed from the base of the PR and between 4c07897 and 2d0b1aa.

📒 Files selected for processing (1)

• README.md

📝 Walkthrough

Walkthrough

This PR updates build-logic to use the main branch instead of master across workflow definitions, scripts, and documentation. Changes include fixing a workflow input definition, updating script branch references, and revising documentation examples and parameter descriptions to reflect the main branch.

Changes

Master to Main Migration

Layer / File(s)	Summary
Workflow Input Definition .github/workflows/subtree-sync.yml	Fixes the subtree_prefix input declaration so required: true and type: string are correctly placed within the workflow input definition.
Script Branch References scripts/vulnerability-scanning/diff-new-cves.sh	Updates Step 1 documentation and user-facing log message to fetch vex/assessments.yaml from liquibase-pro main branch instead of master.
Documentation Updates README.md, CLAUDE.md	README adds optional build_logic_ref input (defaults to main) and updates vulnerability scanning example to checkout liquibase/build-logic at ref: main; CLAUDE.md updates os-extension-test.yml nightly parameter description to reference main-SNAPSHOT instead of master-SNAPSHOT.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• liquibase/build-logic#452: Modifies .github/workflows/subtree-sync.yml and refactors the subtree_prefix variable usage to environment variables.
• liquibase/build-logic#531: Updates scripts/vulnerability-scanning/diff-new-cves.sh with related branch reference changes for the same vex/assessments.yaml fetch operation.

Suggested labels

claude-code-assisted

Suggested reviewers

• jandroav
• filipelautert

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main objective of the changeset: updating references from 'master' to 'main' in documentation and scripts.
Description check	✅ Passed	The description comprehensively explains the purpose of the changes, files affected, and rationale, including why external fossa-cli URLs were intentionally left unchanged.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/master-to-main-refs

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sayaliM0412]

cc: @jandroav @jnewton03 : could you please review. Thank you