chore(master): release 0.6.0
:robot: I have created a release beep boop
0.6.0 (2024-08-04)
Features
- (Hyde power [save|unset]): Added some general options. (e360ad6)
- (Hyde show bookmarks): Remember the top 5 recent selection (c566bbb)
- airplane: adds airplane mode (b0adcb1)
- bookmarks: adds rofi bookmarks selector (2a717c9)
- bookmarks: some additions (57ffdc2)
- completion will be exposed to ./bin/ (1ee024b)
- completion will be exposed to ./bin/ (e2ede9a)
- Hyde --dev convert_cursor /path/to/xcursor (f9ef1bf)
- Hyde cursor []; HyDE cursor Settings (33ff2a3)
- Hyde run airplane_mode: Toggles wifi (87387d8)
-
Hyde show
--rasi ~/path/to/rasi : Supports some Rofi utility to use user theme.rasi (bf49305) - Hyde show bookmark: librewolf bookmarks ) (19a083e)
- Hyde show bookmarks (parse flatpak firefox,etc) (230582a)
- Pastebin improvements (228e6c7)
- screenshot: upload screenshot (1b486bb)
- search: add rofi search feature (125fd52)
- search: add rofi search feature (864d3d0)
- Separate themepatcher implementation but with legacy support (45d2b77)
- Separate themepatcher implementation but with legacy support (8926241)
- Test release (a5f8c86)
- Tries to have a local version of hyde (915ae0d)
- Tries to have a local version of hyde (b383cd0)
- Tries to have a local version of hyde (d1f64f5)
- Tries to have a local version of hyde (f2ef174)
- version.txt (87acf74)
Bug Fixes
- (Hyde show bookmarks): usage (4314c66)
- 0.5.2 > version.txt (d6fe8cb)
- 0.5.2 > version.txt (e0c4630)
- Added NOTIFY function to have async notif (4989ea6)
- give error message when no kde_setting is detected (a89dc96)
- Hyde show bookmark: removes lz4json dep ) (a8edc0d)
- Hyde show bookmarks: have --no-custom (e981439)
- make selections icons consistent (647dc2d)
- Metadata not created (5202a1e)
- minor (dbd3033)
- Patch-Theme (96b2515)
- Patch-Theme (55ff0f8)
- Patch-Theme corrected the args (217ef11)
- Patch-Theme corrected the args (a710516)
- remove usage.md and add faq (5fc539c)
- rename check to enable (21ac35e)
- revert and make version.txt separate (63709d5)
- SDDM create /etc/sddm.conf.d (f53fe2e)
- sddm set: Use echo for / actions (adaea25)
- Setting meta dat borke please update (a2590af)
- spell issues (a890ce7)
- spell issues (e35d8d7)
- theme patch: some hypr.theme parsing (98e30ea)
- Tries to have a local version of hyde (94f67a0)
- Tries to have a local version of hyde (37be716)
- Tries to have a local version of hyde (609a999)
- Tries to have a local version of hyde (772d839)
- Tries to have a local version of hyde (ec9a4c2)
- Tries to have a local version of hyde (b95d043)
- Tries to have a local version of hyde (097921b)
- try: async the update (737ac2d)
- Usage page (89544bc)
This PR was generated with Release Please. See documentation.
@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
I think this one is mature now and the next release might be slower
It borks?