chore(prerelease): prepare and publish release candidate packages

[halvaradop]

Description

This pull request prepares the @aura-stack/auth and @aura-stack/jose packages for their first stable release by publishing release candidate (RC) versions and tagging them with rc on npm.

Note

The @aura-stack/auth package encountered issues related to module augmentation. These issues occurred because the interfaces intended for augmentation were composed using utility types such as Pick and Omit, which cannot be safely augmented and led to unexpected type behavior once the package was published to npm.
Additionally, other issues became visible only after publishing the packages, which explains why more release candidate versions were published than originally expected.

In parallel, the package.json files for both packages were updated to improve metadata and publishing configuration, including:

• Adding homepage and repository links
• Defining publishConfig
• Refining other package configuration options to better support publishing and discoverability

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
auth	Ready	Preview, Comment	Dec 18, 2025 4:24pm
auth-nextjs-demo	Ready	Preview, Comment	Dec 18, 2025 4:24pm

[halvaradop]

After debugging the unexpected behavior in @aura-stack/auth and @aura-stack/jose, I discovered that the issue stems from how the secret key is provided to the createAuth function. While Aura Auth defaults to using the AURA_AUTH_SECRET environment variable, this value is inaccessible to the client-side instance of the auth consumer; therefore, the variable must be prefixed with NEXT_PUBLIC_ to be properly bundled. To prevent similar confusion in the future, we should implement more descriptive error messages to clarify when a required secret is missing or inaccessible on the client.

[halvaradop]

The error was caused by Turborepo not inferring the environment variables configured in the Vercel dashboard; this occurred because these variables must be explicitly added as inputs in the turbo.json configuration file to be recognized during the build process. 5f6581d