Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[3.5.0] This release of Retype has expired. Please update to the latest release. A Retype license is required to continue using this release. #708

Open
saydeicide opened this issue Sep 17, 2024 · 33 comments

Comments

@saydeicide
Copy link

saydeicide commented Sep 17, 2024

after server reatert, i cannot start retype.

$ retype start -n --host 192.168.0.37 --pro
INPUT: /engine/retype
OUTPUT: [in-memory]
ERROR: This release of Retype has expired. Please update to the latest release. A Retype license is required to continue using this release.

i use free version.

@cclypeatus
Copy link

Facing the same issue. Today happens to be the anniversary of v3.5.0, so could it be that the free version gets a year-long license that renews on every release?

@chrstn-opntdc
Copy link

We are encountering the same issue and have a pro license valid until 2027

@altworkz
Copy link

This is also encountered in our setup (Retype Pro v3.5.0).

@geoffreymcgill
Copy link
Collaborator

I am investigating.

@mduft
Copy link

mduft commented Sep 17, 2024

Same issue here :) However in our gradle build where we call npx retypeapp build with the free retype version. I confirmed that there is no old version, 3.5.0 is used.

@ansel-nekuti
Copy link

Same issue here. We're using the free version.

@clabeuhtegrite
Copy link

Same issue here. I use the free version.

@abergdesign
Copy link

Same for us, Ubuntu 24.04, retype 3.5.0 free version

@blueloveTH
Copy link

Same for us, Ubuntu 20.04, retype 3.5.0 free version.

@mduft
Copy link

mduft commented Sep 17, 2024

I know, not much time has passed, however all our builds are stuck on this - any news? I'd prefer not to use ignoreExitCode :D

@kbudde
Copy link

kbudde commented Sep 17, 2024

Affects also the licensed version, just saying 💥

@zakaria-chahboun
Copy link

Same here

@kcowgill
Copy link

Watching. Adding that indeed the licensed version is also affected. The error messaging is slightly different:

❯ retype start --host REDACTED
  INPUT: /Users/kcowgill/docs
 OUTPUT: [in-memory]
ERROR: Failed to access the wallet. This release of Retype has expired. Please update to the latest release. A Retype license is required to continue using this release.
       Please use the "--clear" option to reset the wallet if the problem persists.

I went ahead and cleared the wallet and attempted to re-add our key:

❯ retype wallet --add REDACTED
ERROR: Failed to save the wallet. This release of Retype has expired. Please update to the latest release. A Retype license is required to continue using this release.
ERROR:
         - Status:                       Valid
         - Expires:                      2025-05-15 11:34
         - Max pages:                    1000000

@alec-drw
Copy link

+1

@kcowgill
Copy link

I am investigating.

@geoffreymcgill Any updates?

@geoffreymcgill
Copy link
Collaborator

The fix is in place, but just trying to correct a couple issues with the release/deployment process, then v3.6.0 will be released. I'm working on it right now and will release v3.6.0 immediately after all green on the build.

@geoffreymcgill
Copy link
Collaborator

Retype v3.6.0 has been released.

If you are using the GitHub Action using the @latest tags, your project will automatically pickup and build with the v3.6.0 release upon your next commit to your repo. Just commit a change and your website will build with v3.6.0.

If you are building with Retype on your local machine, updating to the latest release is required, see:

https://retype.com/guides/getting-started/#update

If for some reason running the update command does not actually update your local release, uninstall Retype, then install:

npm uninstall retypeapp --global
npm install retypeapp --global

The Docker containers have not been updated. There is still a small issue with our deployment process that needs to get worked out. This will be the next thing to fix and then I'll make a 3.6.1 release.

Once I'm caught up and everything is stabilized, I'll provide an update and explanation on what happened, plus how this issue will not happen in the future.

I truly apologize the inconvenience this has caused for everyone.

Please let me know if you run into any issues and I will do my best to assist.

@latenitefilms
Copy link

I'm still seeing this on v3.6.0? Maybe my license has expired?

image

@leadenhall
Copy link

The retype --version output includes a SHA appended to the version number, causing the latest GitHub Action to fail the built-in version check.

$ retype --version
3.6.0+6fe53cf630452bb1c91973116e3a4af3297f2556

@geoffreymcgill
Copy link
Collaborator

I'm still seeing this on v3.6.0? Maybe my license has expired?

Hi @latenitefilms. Basically, yes, your key has expired. I will explain below, but if you send me an email to [email protected], I will help get you back online immediately.

Here is the explanation of what's happening...

If you have the license key installed locally, you can run the command retype wallet --list, which will list out all the license keys you have installed. When I test one of your license keys, I see the following:

- Free upgrades until:          2024-05-25 17:39

The Retype license keys technically do not expire. What expires is the window for which free upgrades are available.

Your license key was valid for free upgrades until May 25, 2024.

The previous release of Retype (v3.5.0) was released on Sep 16, 2023. Your key would work for any new releases up to May 5, 2024.

With the release of v3.6.0 on Sep 17, 2024, your Retype Pro license key is no longer available for that free upgrade.

We need to improve the message that is output when that Free upgrades until: date occurs. Sorry about that.

@geoffreymcgill
Copy link
Collaborator

The retype --version output includes a SHA appended to the version number, causing the latest GitHub Action to fail the built-in version check.

Confirmed, I noticed this as well. I am investigating right now.

@latenitefilms
Copy link

I was under the impression we got three years of updates?

https://retype.com/pro/

Has it been three years already?!?

I was also under the impression that if your license expired, it just rolls back to the free version based on this:

https://retype.com/pro/#if-i-do-not-renew-does-my-website-stop-working

@latenitefilms
Copy link

Any news @geoffreymcgill ?

I got your first email, but haven't received any new license keys yet?

I'd love to get this solved ASAP, as I'm using Retype for a news site (FCP Cafe), so it's a bit of a bummer I can't update the site.

@wtrucci
Copy link

wtrucci commented Sep 22, 2024

Retype v3.6.0 has been released.

If you are using the GitHub Action using the @latest tags, your project will automatically pickup and build with the v3.6.0 release upon your next commit to your repo. Just commit a change and your website will build with v3.6.0.

If you are building with Retype on your local machine, updating to the latest release is required, see:

https://retype.com/guides/getting-started/#update

If for some reason running the update command does not actually update your local release, uninstall Retype, then install:

npm uninstall retypeapp --global
npm install retypeapp --global

The Docker containers have not been updated. There is still a small issue with our deployment process that needs to get worked out. This will be the next thing to fix and then I'll make a 3.6.1 release.

Once I'm caught up and everything is stabilized, I'll provide an update and explanation on what happened, plus how this issue will not happen in the future.

I truly apologize the inconvenience this has caused for everyone.

Please let me know if you run into any issues and I will do my best to assist.

Hi, any news on docker image?

@maurxce
Copy link

maurxce commented Oct 2, 2024

Experiencing the same issue, my wiki is not useable anymore due to this.
I deployed it via docker, is there some temporary fix for now?

@latenitefilms
Copy link

In my case, @geoffreymcgill sent me new license keys which did the trick.

@leadenhall
Copy link

The retype --version output includes a SHA appended to the version number, causing the latest GitHub Action to fail the built-in version check.

$ retype --version
3.6.0+6fe53cf630452bb1c91973116e3a4af3297f2556

We are still not able to use the GHA workflow due to this issue. Any updates on that front?

@JoelMTaylor
Copy link

@geoffreymcgill, I have the same issue as latenitefilms. I have sent emails to [email protected], but I haven't received a reply.

@SinsinwarHunk
Copy link

SinsinwarHunk commented Oct 27, 2024

Docker containers have not been updated.

any update for Docker image for the license issue in free version, getting "ERROR: This release of Retype has expired. Please update to the latest release. A Retype license is required to continue using this release."

@latenitefilms
Copy link

@geoffreymcgill - I'm having some issues with some of my other sites too now. I've sent an email. Hopefully it hasn't ended up in your spam filter. Thanks mate!

@latenitefilms
Copy link

@latenitefilms
Copy link

For anyone following along, I was able to get it all working again with this:

    steps:
      - uses: actions/checkout@v4

      - uses: actions/setup-dotnet@v1
        with:
          dotnet-version: 7.0.x

      - uses: retypeapp/action-build@a95ca1f9508dec8465a93f2e50a1228d22e90f4e
        with:
          license: ${{ secrets.RETYPE_SECRET }}

      - uses: retypeapp/action-github-pages@latest
        with:
          update-branch: true

...basically just using an older version of Retype.

@scottsemple
Copy link

I had the same issue. After updating to 3.6.0, I deleted my local repo and re-cloned the remote. Seems to be working now.

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

No branches or pull requests