Skip to content

Fix Erraneous Cases in Migration Skill - #157

Merged
b-per merged 13 commits into
mainfrom
changes/core-migration-improvements
Sep 23, 2026
Merged

b-per merged 13 commits into
mainfrom
changes/core-migration-improvements

Conversation

@ash2shukla

@ash2shukla ash2shukla commented Aug 31, 2026 •

Copy link
Copy Markdown
Contributor

Description

  • Renames upgrading-dbt-core to upgrading-dbt
  • Refreshes upgrade guidance and execution references
  • Updates the version-specific knowledge base for dbt Core and supported adapters
  • Updates the skill registry and plugin versions to publish the renamed skill
    correctly

Checklist

@ash2shukla
ash2shukla requested review from a team and sriramr98 August 31, 2026 13:08
@b-per

b-per commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

Is it ready for review? If so, we'll need to bump the versions.

@sriramr98

Copy link
Copy Markdown
Contributor

Hey @b-per. I have a couple more things I want to push on the next release. I'll push them to this branch so that we can get them all in together.

@b-per
b-per marked this pull request as draft September 2, 2026 16:22
@b-per

b-per commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Thanks @sriramr98
I changed it to draft for now. Feel free to make it a non-draft when it is ready to review and merge

@ash2shukla
ash2shukla marked this pull request as ready for review September 3, 2026 07:06
The exit gate used to trigger the customer's own dbt platform jobs, which run on
the deployment environment's credentials and target schema - very often
production. Verification now stays in the develop session, on the signed-in
user's own development credentials.

On dbt platform the gate is a fixed set of commands run in order, stopping at the
first failure: dbt parse, compile, build, test. In VS Code it is dbt parse alone,
because that profile parses against a synthesized profile with fake credentials,
so anything that connects fails at connection rather than informatively.

migration_jobs.json is decoupled from the gate. It is no longer the source of the
commands to run - it records which job commands the customer must change after
merging. The agent builds it by listing the project's jobs and keeping the ones
on a legacy version, rather than being handed job IDs.
@sriramr98

Copy link
Copy Markdown
Contributor

Hi @b-per . This PR is ready for review.

Renames the KB regen workflow file (its own paths: filter already
pointed at upgrading-dbt-kb.yml, so it stopped self-triggering) and
updates the remaining stale upgrading-dbt-core references left over
from the rename: the README skill table, the pyproject.toml
package-data path, and internal prose/docstrings in the skill's
schema, exec references, and scripts. Also fixes the README
description to say "latest dbt" instead of "latest dbt-core".
@b-per
b-per merged commit 531557e into main Sep 23, 2026
2 checks passed
@b-per
b-per deleted the changes/core-migration-improvements branch September 23, 2026 11:09
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.

3 participants