General maintenance

[nohli]

• Update deprecated theme variables
• Update gradle to fix Android build of example app
• Increase compileSdkVersion to fix Android build of example app
• auto-format

[AlexV525]

We should also raise the environment constraints, right?

[nohli]

I guess the new theme variables were first introduced in Flutter 2.10, updated the constrains.

[AlexV525]

👍

[nohli]

@AlexV525 could you please allow access for the workflow to publish to pub.dev?

FYI I've had the same issue with a new package that the link wouldn't work... But after I moved the package to a verified publisher on pub.dev, it worked without the need to any further authorization.

[AlexV525]

FYI I've had the same issue with a new package that the link wouldn't work... But after I moved the package to a verified publisher on pub.dev, it worked without the need to any further authorization.

Do you mean the pub does not allow unknown publisher packages to update? Or we're having an infra issue? The credential is not owned by me so I'll have to collaborate with the team if necessary.

[AlexV525]

I see the outdated authorization logs. I'll update them or transfer the package to our publisher ASAP.

[nohli]

All I've observed is that the GitHub action prompts you to open a link on pub.dev, which appears to be invalid. However, when the package is associated with a verified publisher, it seems to function seamlessly without needing any link.

I'm open to volunteering and adding it to my account. Still, I remember there being an account from fluttercandies.

Thanks for your assistance 🙏🏽

[AlexV525]

@nohli I've updated the credential and the package has been transferred to fluttercandies.com publisher. Could you verify the publish again?

[nohli]

@AlexV525 thank you, great job!
I've jut restarted the workflow, and now it's published.