Update to Cronicle 0.9.80 which fixes issues in getting job logs

[gkovalechyn]

Important

Update Cronicle version to 0.9.80 in Dockerfile and docker-build.sh to fix job log issues.

• Version Update:
  • Update CRONICLE_VERSION from 0.9.77 to 0.9.80 in Dockerfile.
  • Update VERSION from 0.9.77 to 0.9.80 in docker-build.sh.

^{This description was created by for 112fd41. You can customize this summary. It will automatically update as commits are pushed.}

Summary by CodeRabbit

• Chores
  • Updated Cronicle version to 0.9.80 for Docker builds and related scripts.

[coderabbitai]

Walkthrough

The changes update the Cronicle version from 0.9.77 to 0.9.80 in both the Dockerfile and the docker-build.sh script. No other modifications were made to the build logic, configuration, or script flow.

Changes

File(s)	Change Summary
Dockerfile	Updated CRONICLE_VERSION environment variable from 0.9.77 to 0.9.80
docker-build.sh	Updated VERSION variable from 0.9.77 to 0.9.80

Poem

A hop, a skip, a version jump,
Cronicle’s numbers get a bump!
From seventy-seven to eighty we go,
In Docker’s burrow, updates flow.
The script and file both now agree—
New adventures for Cronicle, yippee!
🐇✨

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.

---

Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 2cc2873 and 112fd41.

📒 Files selected for processing (2)

• Dockerfile (1 hunks)
• docker-build.sh (1 hunks)

🔇 Additional comments (2)

Dockerfile (1)

5-5: Cronicle version bump to 0.9.80
The CRONICLE_VERSION environment variable has been updated correctly to the new release. This aligns the Docker image with the intended Cronicle version.

docker-build.sh (1)

3-3:

✅ Verification successful

Update build script to Cronicle 0.9.80
The VERSION variable has been bumped from 0.9.77 to 0.9.80, matching the Dockerfile change.

Please verify that there are no lingering references to the old version in the repository:

---

🏁 Script executed:

#!/bin/bash
# Verify no stale Cronicle version references remain
set -eo pipefail
OLD="0.9.77"
echo "Searching for references to version ${OLD}..."
rg -n "${OLD}" || echo "✅ No references to ${OLD} found."

Length of output: 222

---

No stale Cronicle version references found
I’ve run a repository-wide search for 0.9.77 and confirmed there are no remaining references. The bump in docker-build.sh to VERSION=0.9.80 is consistent with the Dockerfile and the rest of the codebase.

✨ Finishing Touches

• 📝 Generate Docstrings

---

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 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.

[gemini-code-assist]

Hello @gkovalechyn, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Summary of Changes

Hello, I'm gemini-code-assist, here to provide a summary of this pull request. This PR is focused on updating the version of Cronicle used within the Docker image and its build process. The primary goal, as indicated by the title, is to upgrade to Cronicle version 0.9.80, which is stated to include fixes for issues related to retrieving job logs. The changes are straightforward, involving only updates to version strings in two files.

Highlights

• Cronicle Version Bump: The pull request updates the specified Cronicle version from 0.9.77 to 0.9.80.
• Fixes Job Log Issues: The update to version 0.9.80 is specifically highlighted as addressing existing issues with fetching job logs.

Changelog

• Dockerfile
  • Updated the CRONICLE_VERSION environment variable from 0.9.77 to 0.9.80 on line 5.
• docker-build.sh
  • Updated the VERSION variable from 0.9.77 to 0.9.80 on line 3.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

---

Version number climbs,
Fixing logs, a small change,
Build the image now.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 112fd41 in 1 minute and 8 seconds. Click for details.

• Reviewed 25 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 5 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. Dockerfile:5

• Draft comment:
  Bump CRONICLE_VERSION to 0.9.80. Ensure this release exists on GitHub.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

2. docker-build.sh:3

• Draft comment:
  Updated VERSION variable to 0.9.80 to match Dockerfile.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

3. docker-build.sh:7

• Draft comment:
  Added 'docker scout quickview' for vulnerability overview. Verify that this tool is installed in the build environment.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

4. docker-build.sh:22

• Draft comment:
  Interactive confirmation loop may hinder automation. Consider adding CLI flags or a non-interactive mode.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

5. docker-build.sh:5

• Draft comment:
  Initial 'docker build' is run before the multi-platform build. Confirm if both builds are necessary to avoid redundant work.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

Workflow ID: wflow_9yEPKEwEbl7EcBZn

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[gemini-code-assist]

Code Review

This pull request updates the Cronicle version from 0.9.77 to 0.9.80 in both the Dockerfile and docker-build.sh script. The stated goal is to fix issues related to getting job logs, which is a valuable improvement. The changes are clear, concise, and directly address this objective. Well done on keeping the versions consistent across files!

Summary of Findings

• Cronicle Version Update: The Cronicle version was successfully updated to 0.9.80 in Dockerfile (ENV CRONICLE_VERSION) and docker-build.sh (VERSION variable). This aligns with the pull request's objective to incorporate fixes from the newer Cronicle version, specifically for job log issues.
• Consistency: The version number update is consistent across both modified files, which is good practice for maintainability.

Merge Readiness

The changes in this pull request are straightforward and correctly implement the version update for Cronicle. From a code review perspective of the diff, these changes appear sound and ready for merging. As an AI, I am not authorized to approve pull requests. It's advisable to ensure that Cronicle version 0.9.80 is stable and has been tested for the intended job log fixes before finalizing the merge. No issues requiring changes were identified in the diff based on the review criteria and severity settings.