Skip to content

Automate Nightly Builds as Pre-release Candidates#1114

Merged
goruha merged 3 commits intomainfrom
pre-releases
Mar 6, 2025
Merged

Automate Nightly Builds as Pre-release Candidates#1114
goruha merged 3 commits intomainfrom
pre-releases

Conversation

@goruha
Copy link
Member

@goruha goruha commented Mar 6, 2025

what

  • Pre releases

why

  • Define pre releases

Summary by CodeRabbit

  • Chores
    • Improved the release automation to trigger distribution tasks only for stable (non-prerelease) releases, ensuring a more streamlined and reliable update process.
    • Introduced a new nightly build workflow to automate daily builds and releases.

@goruha goruha requested a review from a team as a code owner March 6, 2025 11:47
@mergify
Copy link

mergify bot commented Mar 6, 2025

Important

Cloud Posse Engineering Team Review Required

This pull request modifies files that require Cloud Posse's review. Please be patient, and a core maintainer will review your changes.

To expedite this process, reach out to us on Slack in the #pr-reviews channel.

@mergify mergify bot added the needs-cloudposse Needs Cloud Posse assistance label Mar 6, 2025
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 6, 2025

📝 Walkthrough

Walkthrough

The changes modify the GitHub Actions workflows by introducing conditional execution for jobs in .github/workflows/build.yml and adding a new workflow in .github/workflows/nightlybuilds.yml. The release and homebrew jobs in the first file will only run if the release event is not marked as a prerelease. The new workflow triggers on manual dispatch or a daily schedule, publishing artifacts as a prerelease.

Changes

File Change Summary
.github/workflows/build.yml Added condition if: ${{ github.event.release.prerelease == false }} to both release and homebrew jobs.
.github/workflows/nightlybuilds.yml Introduced new workflow name: Nightly Builds, triggered manually and daily at 00:15 UTC, with a release job.

Suggested labels

major

Suggested reviewers

  • aknysh

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bb3bc41 and 60009b7.

📒 Files selected for processing (1)
  • .github/workflows/nightlybuilds.yml (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • .github/workflows/nightlybuilds.yml
⏰ Context from checks skipped due to timeout of 90000ms (5)
  • GitHub Check: Build (windows-latest, windows)
  • GitHub Check: Build (ubuntu-latest, linux)
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: Analyze (go)
  • GitHub Check: Summary

🪧 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.
  • @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 or @auto-summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai or @auto-title anywhere in the PR title to generate the title automatically.

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
Contributor

@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 (2)
.github/workflows/build.yml (2)

22-22: Pre-release Conditional Logic & Trailing Space Cleanup.
The new condition for the release job correctly checks that the release is not a pre release, which aligns well with the PR’s objectives. However, static analysis detected trailing spaces at the end of this line. Please remove these spaces to comply with YAML formatting standards.

-    if: ${{ github.event.release.prerelease == false }}  
+    if: ${{ github.event.release.prerelease == false }}
🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 22-22: trailing spaces

(trailing-spaces)


27-27: Conditional Check for Homebrew Job & Formatting.
The update on the homebrew job properly prevents its execution during pre releases. Similar to the release job, there are trailing spaces at the end of this line. Cleaning these up will improve consistency and comply with YAMLlint requirements.

-    if: ${{ github.event.release.prerelease == false }}  
+    if: ${{ github.event.release.prerelease == false }}
🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 27-27: trailing spaces

(trailing-spaces)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5bc5b69 and fba800f.

📒 Files selected for processing (1)
  • .github/workflows/build.yml (1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.35.1)
.github/workflows/build.yml

[error] 22-22: trailing spaces

(trailing-spaces)


[error] 27-27: trailing spaces

(trailing-spaces)

⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Build (windows-latest, windows)
  • GitHub Check: Summary

coderabbitai[bot]
coderabbitai bot previously approved these changes Mar 6, 2025
coderabbitai[bot]
coderabbitai bot previously approved these changes Mar 6, 2025
@codecov
Copy link

codecov bot commented Mar 6, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 17.29%. Comparing base (5bc5b69) to head (60009b7).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1114   +/-   ##
=======================================
  Coverage   17.29%   17.29%           
=======================================
  Files         169      169           
  Lines       18747    18747           
=======================================
  Hits         3242     3242           
  Misses      14908    14908           
  Partials      597      597           
Flag Coverage Δ
unittests 17.29% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@osterman osterman added the no-release Do not create a new release (wait for additional code changes) label Mar 6, 2025
Co-authored-by: Erik Osterman (CEO @ Cloud Posse) <erik@cloudposse.com>
@osterman osterman changed the title Pre releases Implement Nightly Pre-releases Mar 6, 2025
@osterman osterman changed the title Implement Nightly Pre-releases Implement Nightly Builds as Pre-release Candidates Mar 6, 2025
@osterman osterman changed the title Implement Nightly Builds as Pre-release Candidates Automate Nightly Builds as Pre-release Candidates Mar 6, 2025
@goruha goruha merged commit 21ce5b8 into main Mar 6, 2025
49 checks passed
@goruha goruha deleted the pre-releases branch March 6, 2025 16:41
@mergify mergify bot removed the needs-cloudposse Needs Cloud Posse assistance label Mar 6, 2025
@github-actions
Copy link

github-actions bot commented Mar 7, 2025

These changes were released in v1.165.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-release Do not create a new release (wait for additional code changes)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants