Post

Plamen Mushkov
@apexapplab.dev

Having fun with SQLcl - few observations: 🔸 For some reason I had a package that was exported using .pkb and .pks for the body and spec. After I upgraded to the latest version, I now have the package duplicated in my repository, because both files are exported with .sql extension. ... continues ⤵️

Plamen Mushkov
@apexapplab.dev

🔸 I need to delete a release that I have just created. There is no command to do that. Only way is to manually delete the release folder and artifact. But it's not all - if you have used the "!git tag" option (ex. !git tag release-1.1.0), SQLcl will still check for existing tags ... ⤵️

Plamen Mushkov
@apexapplab.dev

... and would not allow reusing the 1.1.0 release number. Here are a few tips - use "!git tag" to list all existing tags. If you see the one that you want gone - use "!git tag -d release-1.1.0". Note: use the tag name exactly as listed - "release-1.1.0" in this case. Any comment and suggestion? 💡

0 reposts0 likes

Plamen Mushkov
@apexapplab.dev

Well, also remove the Release lines from the /dist/releases/main.changelog.xml file. For example, remove this line for release 1.1.0 ⤵️ <include file="1.1.0/release.changelog.xml" relativeToChangelogFile="true"/>

Dan McGhan
@dmcghan.bsky.social

Hi Plamen, did you happen to see this post? danmcghan.hashnode.dev/upgrading-sq... I recommend refreshing 'src/database'. That would have addressed the issue you ran into with the .pks/.pkb extensions changing to .sql. It would also fix other issues that can happen with updates to SQLcl Projects.

danmcghan.hashnode.devUpgrading SQLcl When Using SQLcl ProjectsKeeping your development tools up to date is essential for smooth collaboration and to take advantage of the latest features and fixes. When working with SQLcl Projects, upgrading SQLcl requires a str...
Dan McGhan
@dmcghan.bsky.social

I'm unaware of any ties in SQLcl Projects to Git tags, so any strange behavior there should be revisited. Please let us know if you have a reproducible test case. I suspect the true issue was the one you mentioned later, the fact that the main changelog still had points to the deleted release.