Skip to content

Bug/692 create first release without fail#693

Merged
ArBridgeman merged 6 commits intomainfrom
bug/692_create_first_release_without_fail
Feb 6, 2026
Merged

Bug/692 create first release without fail#693
ArBridgeman merged 6 commits intomainfrom
bug/692_create_first_release_without_fail

Conversation

@ArBridgeman
Copy link
Collaborator

closes #692
closes #630

Checklist

Note: If any of the items in the checklist are not relevant to your PR, just check the box.

For any Pull Request

Is the following correct:

  • the title of the Pull Request?
  • the title of the corresponding issue?
  • there are no other open Pull Requests for the same update/change?
  • that the issue which this Pull Request fixes ("Fixes...") is mentioned?

When Changes Were Made

Did you:

  • update the changelog?
  • update the cookiecutter-template?
  • update the implementation?
  • check coverage and add tests: unit tests and, if relevant, integration tests?
  • update the User Guide & other documentation?
  • resolve any failing CI criteria (incl. Sonar quality gate)?

When Preparing a Release

Have you:

  • thought about version number (major, minor, patch)?
  • checked Exasol packages for updates and resolved open vulnerabilities, if easily possible?

@ArBridgeman ArBridgeman force-pushed the bug/692_create_first_release_without_fail branch from cc29f1b to 75dd35a Compare February 6, 2026 12:22
@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 6, 2026

@ArBridgeman ArBridgeman merged commit c259f41 into main Feb 6, 2026
61 checks passed
@ArBridgeman ArBridgeman deleted the bug/692_create_first_release_without_fail branch February 6, 2026 12:34
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.

Creating first release fails Find a work around for cookiecutter when already in git tracked directory

2 participants