Open github-actions[bot] opened 1 month ago
@kRHYME7 whenever you commit , a pr is created if there is none. If there is a release PR then it gets updated with all the things you did from last release. Make sure your commits are conventional commits based. It tracks it
Also to differentiate the cli version, lets take the tag as a version. Like for now its v0.5.2
Perfect! Thank you so much! Is this all I need to test for now?
yeah . Thats about it. Now everything is set . Whebever you want to relase next version , just merge this pr and done.
Also to differentiate the cli version, lets take the tag as a version. Like for now its v0.5.2
I did not catch it
I mean we can use the tags as the CLI version of Hyde. Right now we are using the commit digest right like xxxxx.
Also if you want to override the version the bot has generated,
git commit --allow-empty -m "chore: release 2.0.0" -m "Release-As: 2.0.0"
Never mind that comment . cat "${etcDir}/.hyde-cli.ver"
where is this file btw. Is it autogenerated ?
I see alright! Will get back to our discussions if I forget. Thanks again!!!!
cool. You can also dm me on discord
Great!
Lets use release tags as stable version from now on and commit based releases van be rolling.
Sadly we can't have a real "stable" one, because upstream HyDE don't release v0.2.0 yet. And that's good because I'm yet trying to formulate some structure for the installer. (will push a dev branch soon)
BTW for development of the installer is .json format fine (will use it as templating for the menus etc )? I am pretty concern with the deps, as HyDE only had jq
so I will use it. I don't want to introduce another deps for a parser unless the HyDE repo do so.
json is fine. Most tools I know use json
@kRHYME7 I think its time to merge this
:robot: I have created a release beep boop
0.6.0 (2024-06-30)
Features
Bug Fixes
This PR was generated with Release Please. See documentation.