Skip to content

fix: add missing deploy status migration (#285 followup) - #295

Merged
erick-GeGe merged 1 commit into
mainfrom
fix/add-missing-deploy-status-migration
Jul 1, 2026
Merged

fix: add missing deploy status migration (#285 followup)#295
erick-GeGe merged 1 commit into
mainfrom
fix/add-missing-deploy-status-migration

Conversation

@erick-GeGe

Copy link
Copy Markdown
Contributor

Description

PR #285 added DOWNLOADING status choices to the Deploy model but did not include the corresponding migration. This caused makemigrations to always detect a pending change. This migration closes that gap.

Issue

  • Github Issue ID.

Checklist before requesting a review

  • I have performed a self-review of my code.
  • My code follows the style guidelines of this project.
  • I have made corresponding changes to the documentation.
  • New and existing tests pass locally with my changes.
  • If this change is a core feature, I have added thorough tests.
  • If this change affects or depends on the behavior of other estela repositories, I have created pull requests with the relevant changes in the affected repositories. Please, refer to our official documentation.
  • I understand that my pull request may be closed if it becomes obvious or I did not perform all of the steps above.

@erick-GeGe
erick-GeGe merged commit 1e2e31b into main Jul 1, 2026
@erick-GeGe
erick-GeGe deleted the fix/add-missing-deploy-status-migration branch July 1, 2026 20:15
jc99k added a commit that referenced this pull request Jul 15, 2026
PR #283 (0040_metered_usage_record) and PR #295
  (0040_auto_20260623_0025 → 0041_auto_20260623_0041) both branched off
  0039_userprofile, leaving two leaf nodes in the core migration graph.
  Add the merge migration so `migrate` has a single graph to apply.
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