Skip to content

[CT-2437] [Bug] Fix when the release test branch gets bumped #92

@emmyoop

Description

@emmyoop

Current State

The *.latest branch gets cut when we are ready to release the first rc with the cut-release-branch.yml action. Currently, this action also bumps the branch to test releases off here.

Problem

The problem is that an rc is not a final release so when the nightly adapter release tests runs, it cannot find the correct version of core and fails.

Possible Solutions

This is a first pass and definitely needs more thought.

  1. Completely remove the step to bump this and do it manually. Not ideal because we will forget.
  2. Somehow make the action smart enough to figure out what the latest is and programmatically determine what branch we should run off. More ideal but I'm not sure how complex this would be.
  3. Remove bumping the latest from cut-release-branch.yml and do it as part of the release when we're doing the first final release. This seems a bit unintuitive that it will happen.
  4. Allow the release-test to use pre-release versions. Will involve figuring out why this step doesn't return the pre-release with the version. Most ideal

Additional Information

dbt-core runs against main so this is not an issue for that repo. This only affects the adapters. Each adapter has a custom update_release_branch.sh script.

dbt-spark does not currently have a release test

dbt-bigquery did not get this bumped and therefore did not break. But that also means it never gets bumped automatically and must be done manually.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions