v1-compat-utils

Sets the minimum-required scope on : Workflow-level -> No changes to jobs, steps, runners, or triggers YAML still parses ( succeeds) Rationale: The test job is read-only; nothing in it needs write access to the repo. Without an explicit block, the run inherits whatever default the repository's actions settings happen to be set to. That default has drifted in the past, and forks-of-forks lose track of it. the OpenSSF Scorecard Token-Permissions check flags missing per-workflow permissions as a finding. After the tj-actions/changed-files supply-chain incident from March 2025, the cost-benefit on explicit minimum scopes is firmly on the side of declaring them.

Hey, Trying to upgrade to newer versions of remix and running into the issue of old peer dependencies on the remix-dev package. Could those be updated, please?

Hi, it seems the v1-route-convention package is causing problems when using the unstable_vitePlugin (see https://github.com/remix-run/remix/issues/8585). I just spend half a day figuring out why the local dev server was stopping unexpectedly and after removing the v1-route-convention package (as described in the above issue it finally starts, but the project is obviously broken now as we haven't migrated to the v2 route convention yet. Before we do that however I was wondering if there are any plans on making the package compatible with the vitePlugin?