Update workflows, documentation, and dependency configuration #120
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Removed unnecessary path filters from the deployment workflow configuration. This change ensures the workflow triggers consistently on changes to relevant branches or pull requests without redundant restrictions.
Added commands to log the home directory paths during the release workflow. This can help in debugging and verifying the environment setup for NPM authentication.
Updated NPM authentication log messages for clarity in `release.yml`. Adjusted deployment workflow triggers to include specific file paths for improved precision in `deploy.yml`.
Added path filters to the release workflow for better control over triggering conditions. Updated NPM authentication step to use the HOME environment variable directly, ensuring compatibility and clarity.
Adjusted the paths section of the release workflow to ensure proper triggering. This change re-adds a previously removed path pattern for package-related files.
Reordered the paths in the workflow triggers to ensure proper evaluation and consistency. This change addresses potential mismatches in path priorities, improving deployment behavior for both push and pull requests.
Replaced `${{ HOME }}` with `$HOME` to correct the syntax in the release workflow file. This ensures proper evaluation and avoids potential issues with environment variable resolution during execution.
Added a step in the setup-environment action to configure the NPM auth token automatically, removing the redundant manual authentication step in the release workflow. This simplifies the CI pipeline and centralizes the configuration for better maintainability.
The NPM_TOKEN environment variable has been commented out in the release workflow. This change prevents its usage during the setup of the CI environment while keeping the configuration for potential future reactivation.
Simplifies the setup-environment action by removing npm registry URL and auth token configuration. The workflow no longer relies on passing the NPM_TOKEN, streamlining the process and reducing complexity. This cleanup removes unused inputs and ensures a more straightforward configuration.
Updated @swc/core devDependency across multiple packages to ^1.11.20 for consistency and to incorporate the latest improvements and fixes. This change ensures alignment with the latest supported version of the SWC compiler.
Updated the Turbo cache key to include `pnpm-lock.yaml` hash, branch name, and commit SHA for improved cache precision. Added multiple restore key fallbacks to enhance cache retrieval and reduce redundant builds.
Introduce steps to enter and exit canary pre-release mode based on branch. Allows managing pre-releases on "canary" and finalizing them on "main". Ensures better release flow handling with changesets.
Added permissions for workflows, configured git user for CI, and improved canary pre-release handling. Integrated changesets action for canary and main branches, syncing main to canary after releases. Updated environment variables for Turbo and adjusted build and publish steps for efficiency.
Introduced separate workflows for canary and production releases to improve clarity and control. Canary releases now only trigger on the `canary` branch, while production releases occur on the `main` branch. Added a new sync workflow to merge `main` into `canary` post-production release.
Added necessary permissions to the deploy workflow to allow reading repository contents and creating comments on issues and pull requests. This ensures the workflow runs smoothly while interacting with PRs and issues.
Revised supported versions to reflect current project status. Added clear instructions for reporting vulnerabilities, including response timelines and remediation procedures. Emphasized commitment to user security and outlined contributor acknowledgment process.
Updated the version numbers in README badges for Next.js, TypeScript, Radix UI, and Tailwind CSS to be less specific. This reduces unnecessary detail and makes the README easier to maintain.
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
|
🚀 Preview deployment is ready! 🔍 Preview URL: https://codefast-kbtksrtuf-codefastlabs.vercel.app |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request includes several updates and enhancements to workflows, documentation, and dependency management:
Workflows:
Documentation:
SECURITY.mdwith supported version policies and clear vulnerability reporting guidelines.Dependencies:
@swc/coredependency to the latest compatible version (^1.11.20).