You have commit messages with errors ⧗ input: Use DeployFromRepository when possible. If the controller has implemented the Application facade of version 19 or higher, use DeployFromRepository method to deploy a charm. This method shortcuts most of the deploy business logic in the client and allows the controller to handle it all. ✖ subject may not be empty [subject-empty] ✖ subject may not end with full stop [subject-full-stop] ✖ type may not be empty [type-empty] ✖ found 3 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: Ensure the url series and origin base match values for AddCharm. Juju 2.9 and 3.1 still require series in the url to work properly. ✖ subject may not be empty [subject-empty] ✖ subject may not end with full stop [subject-full-stop] ✖ type may not be empty [type-empty] ✖ found 3 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: Indicate when the legacy deploy code can be removed. Import for future efforts to know when this can happen. ✖ subject may not be empty [subject-empty] ✖ subject may not end with full stop [subject-full-stop] ✖ type may not be empty [type-empty] ✖ found 3 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: Do not update charm revision and channel at one time. The provider has no way to determine which takes precendence. ✖ subject may not be empty [subject-empty] ✖ subject may not end with full stop [subject-full-stop] ✖ type may not be empty [type-empty] ✖ found 3 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: Fix update by revision and add more checks. Mold the origin used for charm update if a new revision is specified by the user. Details in comments. Otherwise juju will find the latest revision in the channel to use. Also added checks to ensure that the requested revision supports the architecture and operating system currently deployed. ✖ subject may not be empty [subject-empty] ✖ subject may not end with full stop [subject-full-stop] ✖ type may not be empty [type-empty] ✖ found 3 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: Moves plan generator from `utils` package to `testing`. Cherry picked commit, fixed typo in directory name and removed config change from test as it won't work here. Will be added later. ✖ subject may not be empty [subject-empty] ✖ subject may not end with full stop [subject-full-stop] ✖ type may not be empty [type-empty] ✖ found 3 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: chore(deps): bump github.com/hashicorp/terraform-plugin-framework Bumps [github.com/hashicorp/terraform-plugin-framework](https://github.com/hashicorp/terraform-plugin-framework) from 1.5.0 to 1.6.0. - [Release notes](https://github.com/hashicorp/terraform-plugin-framework/releases) - [Changelog](https://github.com/hashicorp/terraform-plugin-framework/blob/main/CHANGELOG.md) - [Commits](https://github.com/hashicorp/terraform-plugin-framework/compare/v1.5.0...v1.6.0) --- updated-dependencies: - dependency-name: github.com/hashicorp/terraform-plugin-framework dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> ✖ body's lines must not be longer than 100 characters [body-max-line-length] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: Adds error check to ReadModel fucntion. This commit adds missed error check aftert we get models. This fix will help to avoid stack trace in some cases. ✖ subject may not be empty [subject-empty] ✖ subject may not end with full stop [subject-full-stop] ✖ type may not be empty [type-empty] ✖