• Add --filter to import-jobs to allow importing jobs to specific environments. In the case where people maintain jobs in the dbt Cloud UI and want to promote them, they can mention what environments they want to import the jobs to using the identifier of the job: [[envs_filter:identifier]].

What's Changed

• Add ability to filter on import by @b-per in #136

Full Changelog: v1.5.0...v1.6.0

What's Changed

• Add --json parameter to plan and sync by @b-per in #135

Full Changelog: v1.4.0...v1.5.0

What's Changed

• Add ability to define field templates when importing jobs by @b-per in #134

Full Changelog: v1.3.2...v1.4.0

What's Changed

• Fix docs links by @b-per in #133

Full Changelog: v1.3.1...v1.3.2

What's Changed

• Make changes output to stdout instead of stderr, keeping stderr for logs by @b-per in #130
• Update docs for 1.3 by @b-per in #132

Full Changelog: v1.3.0...v1.3.1

What's Changed

• Add mkdocs site
• Add --managed-only flag to the import command to only import managed jobs
• Add --environment-id and --project-id flags to link, unlink and deactivate-jobs command

Full Changelog: v1.2.0...v1.3.0

What's Changed

• Link jobs to existing ID when importing jobs by @b-per in #124
  Technically, this is a breaking change but I think that this is the behavior that most people would have expected

Full Changelog: v1.1.0...v1.2.0

What's Changed

• Update jinja2 version by @b-per in #119
• Create CODEOWNERS file by @security-dbtlabs in #120
• Add ability to read from multiple files by @b-per in #123

Full Changelog: v1.0.2...v1.1.0

What's Changed

• Chore: Update release process by @b-per in #118

Full Changelog: v1.0.1...v1.0.2

What's Changed

• Fix issue with plan when adding/removing fields by @b-per in #117

Full Changelog: v1.0.0...v1.0.1