Fix CI/CD pipeline: comprehensive error handling and versioning

[jbdevprimary]

Summary

• Fixed "Remove prohibited files" step in enforce standards workflow - now handles 404s gracefully
• Fixed release workflow to use proper CalVer versioning (was using unconfigured pycalver)
• Decoupled enforce job from sync/release/docs pipeline - failures no longer block releases
• Made docs workflow more robust with better error handling

Changes

1. reusable-enforce-standards.yml: Uses helper function with proper error suppression
2. reusable-release.yml: Inline CalVer (YYYY.MM.BUILD) matching project convention
3. ci.yml: enforce runs in parallel, doesn't block sync
4. reusable-docs.yml: Better path handling, .nojekyll, fallback docs

Test plan

• Verified workflow YAML syntax
• CI should pass on this PR
• Merge to main and verify full pipeline runs

---

Note

Decouples and makes enforce non-blocking, hardens docs deployment, and switches releases to inline CalVer with automatic version update.

• CI Orchestration (.github/workflows/ci.yml)
  • sync no longer waits for enforce (runs in parallel).
  • enforce marked non-blocking; now runs after matrix, test, and lint.
• Release (reusable-release.yml)
  • Add inline CalVer generation (YYYY.M.BUILD) and update __version__ in package via sed.
  • Split build and publish steps; show built artifacts; Twine upload with --skip-existing.
• Docs (reusable-docs.yml)
  • Robust path handling with PKG_DIR; ensure docs/_build.
  • Conditional Sphinx build (requires conf.py); otherwise generate placeholder HTML.
  • Safer gh-pages deployment: create branch if missing, clear/copy, ensure index.html, add .nojekyll, commit only on changes, print deployed URL.
• Standards Enforcement (reusable-enforce-standards.yml)
  • Add delete_file helper with graceful error handling; only delete workflows if directory exists.
  • Remove prohibited files (.github/CODEOWNERS, dependabot.yml, repo-standards.yml); improved summary output.

^{Written by Cursor Bugbot for commit b282ce6. This will update automatically on new commits. Configure here.}

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[Copilot]

Pull request overview

This PR fixes critical issues in the CI/CD pipeline, focusing on error handling and proper versioning implementation. The changes transition from the broken pycalver approach to inline CalVer generation matching the project's established convention (YYYY.MM.BUILD with non-zero-padded months), improve error handling in the enforce standards workflow to gracefully handle missing files, and decouple the enforce job from the release pipeline to prevent blocking.

Key changes:

• Replaced pycalver dependency with inline CalVer generation in release workflow
• Added comprehensive error handling for file deletion operations in enforce standards
• Restructured CI workflow dependencies to run enforce in parallel rather than blocking releases

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 5 comments.

File	Description
.github/workflows/reusable-release.yml	Implements inline CalVer versioning (YYYY.MM.BUILD) to replace broken pycalver, adds version update step that finds and modifies __init__.py
.github/workflows/reusable-enforce-standards.yml	Adds delete_file() helper function with proper 404 handling and error suppression for safe file deletion
.github/workflows/reusable-docs.yml	Improves robustness with better path handling, fallback HTML generation, .nojekyll file creation, and comprehensive error handling
.github/workflows/ci.yml	Decouples enforce job from sync/release dependency chain, allowing it to run in parallel without blocking releases

[Copilot]

The find command may fail silently if $PKG_DIR/src doesn't exist, causing the script to continue with an empty INIT_FILE. Add an explicit check that the source directory exists before running find, or modify the error check on line 46-49 to also verify the directory exists and provide a more specific error message.

Suggested change

	# Check that source directory exists
	if [ ! -d "$PKG_DIR/src" ]; then
	echo "Error: Source directory $PKG_DIR/src does not exist."
	exit 1
	fi

[Copilot]

The pattern gh-pages/.* will match and attempt to delete .git directory, which could corrupt the repository. Exclude .git explicitly: find gh-pages -mindepth 1 -maxdepth 1 ! -name '.git' -exec rm -rf {} + 2>/dev/null || true

Suggested change

	rm -rf gh-pages/* gh-pages/.* 2>/dev/null || true
	find gh-pages -mindepth 1 -maxdepth 1 ! -name '.git' -exec rm -rf {} + 2>/dev/null || true

[Copilot]

The function makes two identical API calls to get the SHA (line 148) and then delete the file (line 151). Consider storing the full response from the first call and extracting both the SHA and using it to verify the file exists, reducing API calls by half.

Suggested change

	# Get file SHA, suppress all errors
	SHA=$(gh api "repos/$REPO/contents/$FILE_PATH" --jq '.sha' 2>/dev/null) || true
	# Get file metadata (including SHA), suppress all errors
	FILE_JSON=$(gh api "repos/$REPO/contents/$FILE_PATH" 2>/dev/null) || true
	SHA=$(echo "$FILE_JSON" | jq -r '.sha') || true

[Copilot]

Using cut to parse the repo URL is fragile. Use bash parameter expansion instead: echo \"✅ Docs deployed to https://${REPO%%/*}.github.io/${REPO##*/}/\"

Suggested change

	echo "✅ Docs deployed to https://$(echo $REPO | cut -d'/' -f1).github.io/$(echo $REPO | cut -d'/' -f2)/"
	echo "✅ Docs deployed to https://${REPO%%/*}.github.io/${REPO##*/}/"

[Copilot]

The hardcoded path packages/extended-data-types should use the $PKG_DIR variable for the current package (defined on line 32) or construct it properly if this is intentionally installing a dependency. If this is meant to be a different package, add a comment explaining why.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.