chore(main): release 1.8.1

[Cliffback]

🤖 I have created a release beep boop

1.8.1 (2025-11-05)

Bug Fixes

• prevent false configuration changed warning (#11) (d0359a0)

---

This PR was generated with Release Please. See documentation.

[woj-tek]

(huge appologies in advance for hijacking the PR, but there are no issues/discussion section and the original repo was archived and is in R/O mode)

I spend some time trying to install LetMeReShade and was reading everything in @itsOwen original repository (yes, I saw that it was archived) just to finaly find this issue: itsOwen/LetMeReShade#56 which pointed to itsOwen/LetMeReShade#54 (comment) which made me realize tha there is this fork that is maintained :)

Would it be maybe possible to:

• enable issues/discussion in this repo?
• maybe add a comment in the original project readme pointing to this repo?
• or maybe create LetMeReShade org and transfer original project to it making it easier to collaborate withough putting pressure on no single owners account?

[Cliffback]

(huge appologies in advance for hijacking the PR, but there are no issues/discussion section and the original repo was archived and is in R/O mode)

No problem at all! Didn't realise the issues / discussion sections were disabled.

• enable issues/discussion in this repo?

Opened them up now, so feel free to add issues and such

• maybe add a comment in the original project readme pointing to this repo?

Yeah, I can mention it to him, and see if he wants to just add a note or something

• or maybe create LetMeReShade org and transfer original project to it making it easier to collaborate withough putting pressure on no single owners account?

This is a good idea! Would totally be open for something like that as well if more people are interested in helping out.

[itsOwen]

Let's go, baby! I'm glad the project is being maintained, as it was one of the best Steam Deck plugins for me, at least.

I will update the original repo to point to this new one. Also, I recommend asking the Decky support team to replace the old version with your repo.

Thanks for maintaining the project, @Cliffback!

[Cliffback]

Let's go, baby! I'm glad the project is being maintained, as it was one of the best Steam Deck plugins for me, at least.

I will update the original repo to point to this new one. Also, I recommend asking the Decky support team to replace the old version with your repo.

Thanks for maintaining the project, @Cliffback!

Awesome, thank you! I'll look into get it out on the decky store!

[Cliffback]

@itsOwen Do you have any insights or learnings from the publishing part? If there are any pitfalls to avoid?

[woj-tek]

No problem at all! Didn't realise the issues / discussion sections were disabled.
Opened them up now, so feel free to add issues and such

Thank you! 🫶

This is a good idea! Would totally be open for something like that as well if more people are interested in helping out.

I'm not sure I would be of much help as right now I'm at the point of actually trying to run LetMeReShade (and having issues with it hence looking for some help 🫣 :) ) and not that much experience with TypeScrip.

Alas, I still think it would be a good idea for futureproofing the project. And there is also a wiki section, which seems to diverge from main readme.md when it comes to installation details, so I could maybe/possible add a couple of pointers from my experience there :)

[Cliffback]

Closing, as the PR had the wrong branch name, and release please created another with the correct, so got a duplicate

[itsOwen]

@itsOwen Do you have any insights or learnings from the publishing part? If there are any pitfalls to avoid?

yes just follow the decky guidelines and I guess you are good. I had so much plan for this plugin I was working on a major update to solve so many issues and stuff but I stopped I don't have it in me to work on this anymore tbh. Now I just like to chill in my freetime.

But yea you are good to go with the project in ots currenr stage.

[Cliffback]

yes just follow the decky guidelines and I guess you are good. I had so much plan for this plugin I was working on a major update to solve so many issues and stuff but I stopped I don't have it in me to work on this anymore tbh. Now I just like to chill in my freetime.

But yea you are good to go with the project in ots currenr stage.

Yeah, totally get all that! But you did an amazing job with the project! I'm just happy that we can make it live longer!

Would be very happy for a link or note in the original archived project about this 😄

Btw. what's the reason for having your own repositories for the binaries instead of direct urls?

[itsOwen]

@Cliffback

Would be very happy for a link or note in the original archived project about this 😄

Yes, I’ll add it tomorrow.

Btw. what's the reason for having your own repositories for the binaries instead of direct urls?

It was just easier for me to keep all binaries in one place. Direct linking works too if you prefer.

[Cliffback]

@Cliffback

Would be very happy for a link or note in the original archived project about this 😄

Yes, I’ll add it tomorrow.

Btw. what's the reason for having your own repositories for the binaries instead of direct urls?

It was just easier for me to keep all binaries in one place. Direct linking works too if you prefer.

Nice! I'll probably use direct links then, and set up some automation for checking for new ReShade releases, to make updates easeier!

[itsOwen]

@Cliffback You can do that but you have to make two versions.

One with automated updates of reshade that you can post on github (which I was doing earlier but had to change due to decky guidelines)

I recommend you read up on that a little bit or ypu can ask in the discord.

[Cliffback]

@Cliffback You can do that but you have to make two versions.

One with automated updates of reshade that you can post on github (which I was doing earlier but had to change due to decky guidelines)

I recommend you read up on that a little bit or ypu can ask in the discord.

Yeah, I actually meant an automatic GitHub action that creates a PR with the update, and setting the correct version for the specific release, and not auto getting the latest from the plugin itself (which would have been cool though, but sounds like it would be best to avoid this because of the aforementioned guidelines)