release/v0.13.0 #127
Merged
release/v0.13.0 #127
Conversation
This file contains 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
accidental add
…x' of https://github.com/fivetran/dbt_zendesk into release/solve-time-metrics-and-holiday-work-schedule-fix
fix(int_zendesk__schedule_spine): offset holiday start and end time too
…holiday-work-schedule-fix Add new solve time metrics
bugfix/holidat-utc-offset
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Batch PR Overview
This PR will result in the following new package version:
v0.13.0Link all relevant PRs that are included in this release PR
Provide the finalized CHANGELOG entry which details the relevant changes included in this PR:
Batch PR Checklist
Basic Validation
Please acknowledge that you have successfully performed the following commands locally:
Before marking this PR as "ready for review" the following have been applied:
Detailed Validation
Please share any and all of your validation steps. Please highlight any validations that need to be considered following the multiple changes being merged together:
Please see the respective PRs for detailed validation efforts. As both of these PRs are dealing with different pieces of the package I don't feel there is a need to validate the two components together. I did validate that the code does run as expected and test are all passing. As such, I am reasonably comfortable these updates are sufficiently validated and ready to be rolled out.
Provide an emoji that best describes your current mood
📲