fix: set version env var - #1140
Conversation
WalkthroughThe publish workflow now exports WRITER_FRAMEWORK_VERSION from the extracted tag version and prefixes the install step command with this environment variable. No other steps or logic were changed. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
actor Dev as Developer
participant GH as GitHub Actions
participant EV as Extract Version Step
participant CI as Install Step
participant Pub as Publish Step
Dev->>GH: Push tag
GH->>EV: Run extract_version
EV-->>GH: outputs.version
GH->>CI: Run "alfred install.ci"<br/>with env WRITER_FRAMEWORK_VERSION=outputs.version
CI-->>GH: Install completes
GH->>Pub: Continue publish workflow
Pub-->>Dev: Release process proceeds
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing touches🧪 Generate unit tests
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro Disabled knowledge base sources:
📒 Files selected for processing (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (13)
🔇 Additional comments (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🧪 Early access (Sonnet 4.5): enabledWe are currently testing the Sonnet 4.5 model, which is expected to improve code review quality. However, this model may lead to increased noise levels in the review comments. Please disable the early access features if the noise level causes any inconvenience. Note:
Comment |
There was a problem hiding this comment.
HackerOne Code Security Review
🟢 Scan Complete: 1 Issue(s)
🟠 Validation Complete: One or more Issues looked potentially actionable, so this was escalated to our network of engineers for manual review. Once this is complete you'll see an update posted.
Here's how the code changes were interpreted and info about the tools used for scanning.
📖 Summary of Changes
The GitHub Actions workflow configuration for publishing was modified to include an additional environment variable WRITER_FRAMEWORK_VERSION during the dependency installation and code generation phase. This variable is dynamically set using the version extracted from the current tag, potentially enabling version-specific build or deployment behaviors.
| File | Summary |
|---|---|
| .github/workflows/publish.yml | The workflow file was updated to include an additional environment variable WRITER_FRAMEWORK_VERSION when running the "install ci dependencies and generate code" step, which is set to the extracted version from the tag. |
ℹ️ Issues Detected
NOTE: These may not require action!
Below are unvalidated results from the Analysis Tools that ran during the latest scan for transparency. We investigate each of these for accuracy and relevance before surfacing them as a potential problem.
How will I know if something is a problem?
When validation completes, any concerns that warrant attention prior to merge will be posted as inline comments. These will show up in 2 ways:
- Expert review (most cases): Issues will be posted by experts who manually reviewed and validated them. These are real HackerOne engineers (not bots) reviewing through an integrated IDE-like tool. You can communicate with them like any other reviewer. They'll stay assigned and get notified with commit & comment updates.
- Automatically: In cases where our validation checks have highest confidence the problem is legitimate and urgent. These will include a description of contextual reasoning why & actionable next steps.
| File & Line | Issue |
|---|---|
.github/workflows/publish.yml Line 52 |
The change adds an environment variable 'WRITER_FRAMEWORK_VERSION' to the CI installation command, which is derived from user-controlled input (GitHub tag). While the tag format is validated with a regex pattern, this value is passed directly to a command without additional validation. If the 'alfred install.ci' script uses this environment variable in an unsafe way (like in shell commands or eval statements), it could potentially lead to command injection. |
🧰 Analysis tools
- [ ✅ ] HackerOne AI Code Analysis
- [ ✅ ] HackerOne AI Code Validation
- [ ✅ ] semgrep
- [ ✅ ] bandit
Summary by CodeRabbit
Chores
Notes