feat: surface extra mise.toml packages in build output#546
Open
constantinexanthos wants to merge 1 commit intorailwayapp:mainfrom
Open
feat: surface extra mise.toml packages in build output#546constantinexanthos wants to merge 1 commit intorailwayapp:mainfrom
constantinexanthos wants to merge 1 commit intorailwayapp:mainfrom
Conversation
Resolves railwayapp#419. When users define additional packages in their mise.toml (beyond what Railpack providers auto-detect), those package names now appear in the install step output. This gives users visibility into all packages being installed during the build.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #419
Problem
When users define additional packages in their
mise.toml(e.g.redis,terraform), those packages are installed during the build but never shown in the output. The install step only lists packages that Railpack's providers auto-detected, leaving users with no visibility into what else is being installed.Solution
After collecting provider-detected packages, the build step now reads the user's mise config files, parses the
[tools]section, and appends any extra package names (not already tracked by providers) to the install step's display name.Before:
install mise packages: bun, nodeAfter:
install mise packages: bun, node, go, pythonChanges
core/generate/mise_step_builder.go: Parse user mise.toml files for extra tool names and include them in build outputmise-configsnapshot to reflect the new outputTesting