feat: add weekly dev-canary release pipeline#2334
Merged
Vasilije1990 merged 1 commit intodevfrom Mar 11, 2026
Merged
Conversation
Introduces an automated canary release pipeline that: - Runs every Monday at 06:00 UTC (weekly) and on manual dispatch - Gates on basic test suite before publishing - Publishes PEP 440 dev pre-releases to PyPI (e.g. 0.5.4.dev20260309) - Pushes Docker images tagged dev-canary + versioned canary tag - Integrated into release_test.yml for on-demand canary from release pipeline Install via: pip install cognee --pre Docker via: docker pull cognee/cognee:dev-canary Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: vasilije <vas.markovic@gmail.com>
Contributor
WalkthroughIntroduces a new GitHub Actions workflow for automated dev canary releases that triggers on a schedule, manual dispatch, and workflow calls. The workflow performs version computation with UTC-based suffixing, gates via existing tests, and publishes both PyPI packages and Docker images to separate registries. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
.github/workflows/release_test.yml (1)
19-25: Consider whether running both load-tests and basic_tests is intentional.When triggered via
release_test.yml, the test sequence will be:
load-tests(from release_test.yml)test-gate→basic_tests(from dev_canary_release.yml)If
basic_testsis a subset of or overlaps withload-tests, you may be able to skip thetest-gatejob when called viaworkflow_callto reduce CI time. However, if they test different aspects, the redundancy provides additional safety.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/workflows/release_test.yml around lines 19 - 25, The dev-canary-release invocation causes both load-tests and basic_tests to run (via the test-gate in dev_canary_release.yml), which can be redundant; update the workflow to avoid running test-gate/basic_tests when release_test.yml already ran load-tests by adding a guard: add a workflow_call input or use github.event_name/context to detect being called from release_test.yml and then conditionally skip the test-gate job (or remove the dependency) inside dev_canary_release.yml; specifically, modify the dev-canary-release job invocation or the test-gate job in dev_canary_release.yml (referencing job name test-gate and step/basic_tests) to include an if condition (e.g., only run when input.run_test_gate == 'true' or when github.event_name != 'workflow_call_from_release_test') and pass that input from release_test.yml when calling dev-canary-release.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/dev_canary_release.yml:
- Around line 47-57: The canary version computation (step "Compute canary
version" using variables BASE_VERSION, CLEAN_VERSION, CANARY_VERSION) is only
date-unique and will collide for same-day reruns; change the CANARY_VERSION
generation to append a finer-grained timestamp or unique run identifier (e.g.,
include hour/minute or use GITHUB_RUN_ID/GITHUB_RUN_NUMBER) instead of just date
-u +%Y%m%d, and update the CANARY_VERSION export/echo to use that new value so
each workflow run produces a unique PEP 440-compliant dev suffix.
---
Nitpick comments:
In @.github/workflows/release_test.yml:
- Around line 19-25: The dev-canary-release invocation causes both load-tests
and basic_tests to run (via the test-gate in dev_canary_release.yml), which can
be redundant; update the workflow to avoid running test-gate/basic_tests when
release_test.yml already ran load-tests by adding a guard: add a workflow_call
input or use github.event_name/context to detect being called from
release_test.yml and then conditionally skip the test-gate job (or remove the
dependency) inside dev_canary_release.yml; specifically, modify the
dev-canary-release job invocation or the test-gate job in dev_canary_release.yml
(referencing job name test-gate and step/basic_tests) to include an if condition
(e.g., only run when input.run_test_gate == 'true' or when github.event_name !=
'workflow_call_from_release_test') and pass that input from release_test.yml
when calling dev-canary-release.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: c0e0edf4-0b1f-4e81-b569-d72bddf3f113
📒 Files selected for processing (2)
.github/workflows/dev_canary_release.yml.github/workflows/release_test.yml
Comment on lines
+47
to
+57
| - name: Compute canary version | ||
| id: version | ||
| run: | | ||
| BASE_VERSION="$(uv version --short)" | ||
| # Strip any existing .devN suffix to get the base | ||
| CLEAN_VERSION="${BASE_VERSION%%\.dev*}" | ||
| # PEP 440 dev release: 0.5.4.dev20260309 | ||
| CANARY_VERSION="${CLEAN_VERSION}.dev$(date -u +%Y%m%d)" | ||
| echo "version=${CLEAN_VERSION}" >> "$GITHUB_OUTPUT" | ||
| echo "canary_version=${CANARY_VERSION}" >> "$GITHUB_OUTPUT" | ||
| echo "Canary version: ${CANARY_VERSION}" |
Contributor
There was a problem hiding this comment.
Same-day reruns will produce identical canary versions.
The version computation uses date -u +%Y%m%d, meaning multiple workflow runs on the same UTC day produce the same version string. The second PyPI publish will fail because the version already exists.
Consider appending hour/minute or a run number for uniqueness, or document this as expected behavior where concurrency control prevents conflicts.
💡 Optional: Add time component for uniqueness
# PEP 440 dev release: 0.5.4.dev20260309
- CANARY_VERSION="${CLEAN_VERSION}.dev$(date -u +%Y%m%d)"
+ CANARY_VERSION="${CLEAN_VERSION}.dev$(date -u +%Y%m%d%H%M)"Note: This changes the version format to include hour/minute (e.g., 0.5.4.dev202603090600), which is still PEP 440 compliant but may be less readable. Alternatively, rely on concurrency control and document that only one canary per day is published.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| - name: Compute canary version | |
| id: version | |
| run: | | |
| BASE_VERSION="$(uv version --short)" | |
| # Strip any existing .devN suffix to get the base | |
| CLEAN_VERSION="${BASE_VERSION%%\.dev*}" | |
| # PEP 440 dev release: 0.5.4.dev20260309 | |
| CANARY_VERSION="${CLEAN_VERSION}.dev$(date -u +%Y%m%d)" | |
| echo "version=${CLEAN_VERSION}" >> "$GITHUB_OUTPUT" | |
| echo "canary_version=${CANARY_VERSION}" >> "$GITHUB_OUTPUT" | |
| echo "Canary version: ${CANARY_VERSION}" | |
| - name: Compute canary version | |
| id: version | |
| run: | | |
| BASE_VERSION="$(uv version --short)" | |
| # Strip any existing .devN suffix to get the base | |
| CLEAN_VERSION="${BASE_VERSION%%\.dev*}" | |
| # PEP 440 dev release: 0.5.4.dev20260309 | |
| CANARY_VERSION="${CLEAN_VERSION}.dev$(date -u +%Y%m%d%H%M)" | |
| echo "version=${CLEAN_VERSION}" >> "$GITHUB_OUTPUT" | |
| echo "canary_version=${CANARY_VERSION}" >> "$GITHUB_OUTPUT" | |
| echo "Canary version: ${CANARY_VERSION}" |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.github/workflows/dev_canary_release.yml around lines 47 - 57, The canary
version computation (step "Compute canary version" using variables BASE_VERSION,
CLEAN_VERSION, CANARY_VERSION) is only date-unique and will collide for same-day
reruns; change the CANARY_VERSION generation to append a finer-grained timestamp
or unique run identifier (e.g., include hour/minute or use
GITHUB_RUN_ID/GITHUB_RUN_NUMBER) instead of just date -u +%Y%m%d, and update the
CANARY_VERSION export/echo to use that new value so each workflow run produces a
unique PEP 440-compliant dev suffix.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
dev_canary_release.ymlworkflow that publishes canary releases from thedevbranchrelease_test.ymlso canary can also be triggered after load tests passHow it works
.devNsuffix frompyproject.toml, appends.dev{YYYYMMDD}(PEP 440 compliant)pip install cognee --preorpip install cognee==0.5.4.dev20260309)cognee/cognee:dev-canary(rolling) +cognee/cognee:0.5.4.dev20260309(pinned)Usage
pip install cognee --predocker pull cognee/cognee:dev-canaryTest plan
0.5.4.dev20260309)pip install cognee --prepicks up the canary releasedocker pull cognee/cognee:dev-canaryworks after publish🤖 Generated with Claude Code
Summary by CodeRabbit
Release Notes