Fix publish job permissions

[ejfine]

Why is this change necessary?

The publish job is currently missing permission to push the git tag
https://github.com/LabAutomationAndScreening/pyalab/actions/runs/16704553688/job/47280840075

How does this change address the issue?

Adds permission

What side effects does this change have?

None

How is this change tested?

Can't until after merge

Other

Also handled #54
Also bumped up the sleep time for PyPI index to populate since there have been cases where 60s was not enough

Summary by CodeRabbit

• Chores
  • Increased wait time before package installation from PyPI registries to improve reliability.
  • Enhanced confirmation step to display the Python version before importing the installed package.
  • Updated workflow permissions to support git tag creation.

[coderabbitai]

Walkthrough

The GitHub Actions workflow template was updated to increase sleep durations before package installations from PyPI, enhance import verification by printing the Python version, and grant contents: write permission to the create-tag job for tag pushing. No other logic or error handling changes were introduced.

Changes

Cohort / File(s)	Change Summary
Workflow Timing and Import Check Updates template/.github/workflows/publish.yaml.jinja	Increased sleep time from 60s to 90s before PyPI installs; Python import check now prints version.
Workflow Permissions template/.github/workflows/publish.yaml.jinja	Added permissions: contents: write to the create-tag job for git tag pushing.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Poem

A rabbit hops through YAML fields,
With longer naps before it yields.
Python versions now appear—
Tagging granted rights this year.
Workflows polished, neat and bright,
The CI garden feels just right!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f5ac207 and c7ece3f.

📒 Files selected for processing (1)

• template/.github/workflows/publish.yaml.jinja (2 hunks)

🔇 Additional comments (5)

template/.github/workflows/publish.yaml.jinja (5)

188-188: LGTM! Sleep time increase addresses PyPI index population delay.

The increase from 60s to 90s for the PyPI index update aligns with the PR objectives and addresses observed cases where the shorter wait was insufficient.

---

194-194: LGTM! Enhanced import verification with Python version info.

Adding Python version information improves debugging capability when testing package imports across the matrix of Python versions.

---

200-201: LGTM! This fixes the core issue with tag pushing permissions.

Adding contents: write permission to the create-tag job directly addresses the stated problem where the publish job lacked necessary permissions to push git tags, which was causing GitHub Actions workflow failures.

---

283-283: LGTM! Consistent sleep time increase for primary PyPI.

The increase from 60s to 90s matches the staging change and ensures consistent behavior for PyPI index population delays across both staging and primary installations.

---

289-289: LGTM! Consistent import verification enhancement.

Adding Python version information to the primary installation job maintains consistency with the staging job and provides the same debugging benefits across both installation verification steps.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch publish-perms

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[Copilot]

Pull Request Overview

This PR fixes missing permissions for the publish job's git tag creation and improves PyPI index update reliability. The primary issue was that the GitHub Actions workflow lacked the necessary contents: write permission to push git tags, causing the publish job to fail.

Key changes:

• Added contents: write permission to the create-tag job
• Increased PyPI index update wait time from 60s to 90s for better reliability
• Enhanced import test commands to display Python version information

[Copilot]

[nitpick] The Python version print statement adds debugging information but makes the command less focused. Consider separating the version check into a distinct step or making it conditional for cleaner separation of concerns.