Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolve failing alpha package automation #26

Merged
merged 1 commit into from
Jan 28, 2025
Merged

Conversation

NeonDaniel
Copy link
Member

@NeonDaniel NeonDaniel commented Jan 28, 2025

Update actions versions in release_workflow.yml to latest versions
Update Python version to supported 3.10
Addresses failing action run: https://github.com/OpenVoiceOS/ovos-PHAL-plugin-wallpaper-manager/actions/runs/13010883232/job/36288168593
Updates pypi-publish action per project readme

Summary by CodeRabbit

  • Chores
    • Updated GitHub Actions workflow configuration
    • Upgraded GitHub Actions checkout and setup actions to latest versions
    • Updated Python version from 3.8 to 3.10
    • Replaced PyPI publishing action with newer version

Copy link

coderabbitai bot commented Jan 28, 2025

Walkthrough

The pull request updates the GitHub Actions workflow configuration file .github/workflows/release_workflow.yml. The changes primarily involve upgrading the versions of GitHub Actions used in both the publish_pypi and propose_release jobs. The key modifications include updating checkout and Python setup actions to their latest versions, and changing the Python version from 3.8 to 3.10. These updates aim to ensure compatibility and leverage the latest features of the GitHub Actions ecosystem.

Changes

File Changes
.github/workflows/release_workflow.yml - Updated actions/checkout from v2/v3 to v4
- Updated actions/setup-python from v1/v2 to v5
- Changed Python version from 3.8 to 3.10
- Updated PyPI publish action from master to release/v1

Suggested Reviewers

  • JarbasAl

Poem

🐰 Workflows dancing, versions anew,
Actions upgraded with a bunny's view
Python leaps from 3.8 to 3.10
GitHub magic, our release workflow's spin
Hopping forward with CI delight! 🚀


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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. (Beta)
  • @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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
.github/workflows/release_workflow.yml (1)

Line range hint 22-31: Consider updating actions in the notify job for consistency.

While the main workflow changes look good, consider updating these actions in the notify job for consistency:

  • Update actions/checkout@v2 to @v4
  • Consider updating fadenb/[email protected] to a newer version if available
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 9d93d1d and 34930f8.

📒 Files selected for processing (1)
  • .github/workflows/release_workflow.yml (3 hunks)
🔇 Additional comments (3)
.github/workflows/release_workflow.yml (3)

59-62: Good improvement using a stable release tag.

Switching from @master to @release/v1 for the PyPI publish action provides better stability and security.


71-78: LGTM! Consistent action versions across jobs.

The updates maintain consistency with the publish_pypi job and use the latest stable releases of all actions.


42-50: LGTM! Action versions and Python update look good.

The updates to the latest versions of actions and Python 3.10 align with the PR objectives and best practices.

Let's verify Python version compatibility with project dependencies:

✅ Verification successful

Python 3.10 update is compatible with project requirements

The project explicitly supports Python 3.10 in setup.py, and no conflicting version requirements were found in the dependencies.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if setup.py or requirements.txt specify any Python version constraints
rg -l "python_requires|Programming Language :: Python" setup.py requirements.txt 2>/dev/null

# Check for any potential compatibility issues in dependencies
if [ -f "requirements.txt" ]; then
    echo "Checking requirements.txt for Python 3.10 compatibility..."
    pip index versions $(cat requirements.txt | grep -v '^#' | cut -d'[' -f1) 2>/dev/null | grep -i "Requires-Python"
fi

Length of output: 466


Script:

#!/bin/bash
# Check setup.py for Python version constraints
echo "=== Python version constraints in setup.py ==="
rg "python_requires|Programming Language :: Python" setup.py -A 2 -B 2

# Get detailed package requirements
echo -e "\n=== Package requirements ==="
if [ -f "requirements.txt" ]; then
    cat requirements.txt
fi

# Check if any packages specify Python version constraints
echo -e "\n=== Checking specific package Python requirements ==="
if [ -f "requirements.txt" ]; then
    while IFS= read -r pkg; do
        # Skip empty lines and comments
        [[ -z "$pkg" || "$pkg" =~ ^#.*$ ]] && continue
        # Extract base package name without version specifiers
        base_pkg=$(echo "$pkg" | cut -d'[' -f1 | cut -d'>' -f1 | cut -d'<' -f1 | cut -d'=' -f1 | tr -d ' ')
        echo "Checking $base_pkg..."
        pip index versions "$base_pkg" 2>/dev/null | grep -i "Requires-Python:" | head -n1
    done < requirements.txt
fi

Length of output: 2588

@JarbasAl JarbasAl merged commit 7f205ab into dev Jan 28, 2025
6 checks passed
@JarbasAl JarbasAl deleted the FIX_ReleaseWorkflow branch January 28, 2025 17:22
NeonDaniel added a commit to NeonGeckoCom/NeonCore that referenced this pull request Jan 28, 2025
# Description
Update wallpaper plugin to resolve observed issue where default
wallpaper is missing from options

# Issues
- Implements
OpenVoiceOS/ovos-PHAL-plugin-wallpaper-manager#24
- Needs
OpenVoiceOS/ovos-PHAL-plugin-wallpaper-manager#26

# Other Notes
<!-- Note any breaking changes, WIP changes, requests for input, etc.
here -->
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