feat(dakota): update ISOs to alpha2, add alpha1/alpha2 blog post links#597
Conversation
- Update DakotaDownloadCard ISO URLs from latest to alpha2 slugs: dakota-live-alpha2.iso / dakota-nvidia-live-alpha2.iso - Add Alpha 1 and Alpha 2 announcement links in DakotaScene hero below the alpha warning badge Assisted-by: Claude claude-opus-4-5 via pi
📝 WalkthroughWalkthroughThe Dakota component is updated for the alpha2 release: the download card's ISO links now target ChangesDakota Alpha2 Release Updates
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Comment |
There was a problem hiding this comment.
Pull request overview
This PR updates the Dakota landing/download experience for the Alpha 2 release and adds links to the Alpha 1/Alpha 2 announcements.
Changes:
- Adds Dakota Alpha 1 and Alpha 2 announcement links below the alpha warning badge.
- Updates Dakota ISO and checksum download URLs/filenames from
latesttoalpha2.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
src/components/dakota/DakotaScene.vue |
Adds styled release announcement links to the Dakota hero scene. |
src/components/dakota/DakotaDownloadCard.vue |
Points AMD/Intel and Nvidia download entries to Alpha 2 ISO/checksum filenames. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/components/dakota/DakotaScene.vue`:
- Around line 138-143: The .release-links CSS uses hardcoded pixel values (gap:
12px 20px; margin-top: 10px) which violates the no-px rule; replace these with
tokenized/rem or Tailwind spacing utilities: convert gap and margin-top to
equivalent rem/token values or use Tailwind classes (e.g., gap-x-? gap-y-? and
mt-?) instead, updating the .release-links usage in DakotaScene.vue (and any
template markup) so spacing comes from design tokens/Tailwind rather than
explicit px values.
- Around line 37-48: In DakotaScene.vue replace the hardcoded anchor labels
"Alpha 2 Announcement →" and "Alpha 1 Announcement →" with i18n lookups (e.g.
use this.$t or $t in the template like {{ $t('dakota.alpha2Announcement') }} and
{{ $t('dakota.alpha1Announcement') }} and add corresponding keys in your locale
files), and update the .release-links CSS rules to use rem units by changing
gap: 12px 20px; to gap: 0.75rem 1.25rem; and margin-top: 10px; to margin-top:
0.625rem; so the component (DakotaScene and its .release-links class) uses
localized text and rem-based spacing.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: b9ed5087-1d34-4938-abd0-95b5fb7d807e
📒 Files selected for processing (2)
src/components/dakota/DakotaDownloadCard.vuesrc/components/dakota/DakotaScene.vue
| <div class="release-links"> | ||
| <a | ||
| href="https://docs.projectbluefin.io/blog/making-our-own-fate/" | ||
| target="_blank" | ||
| rel="noopener noreferrer" | ||
| >Alpha 2 Announcement →</a> | ||
| <a | ||
| href="https://docs.projectbluefin.io/blog/dakota-alpha-1/" | ||
| target="_blank" | ||
| rel="noopener noreferrer" | ||
| >Alpha 1 Announcement →</a> | ||
| </div> |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify existing vue-i18n usage/key style before adding new keys.
rg -n --type=vue "useI18n|\\bt\\('" src/components
rg -n "DakotaScene|Release|Alpha|Announcement" src --glob '*.{json,yml,yaml,ts,vue}'
fd -i 'locale|locales|i18n' srcRepository: projectbluefin/website
Length of output: 3130
🏁 Script executed:
cat -n src/components/dakota/DakotaScene.vue | head -60Repository: projectbluefin/website
Length of output: 2467
🏁 Script executed:
cat -n src/components/dakota/DakotaScene.vue | sed -n '130,165p'Repository: projectbluefin/website
Length of output: 1003
🏁 Script executed:
rg -n "useI18n" src/components/dakota/DakotaScene.vueRepository: projectbluefin/website
Length of output: 48
Externalize announcement labels to i18n and use rem-based spacing.
Two issues to address:
-
User-facing text must be externalized. The announcement link labels ("Alpha 2 Announcement →" and "Alpha 1 Announcement →") are hardcoded in the template and should use i18n keys as per guidelines.
-
Use rem units instead of hardcoded pixels in
.release-links. Replacegap: 12px 20px;withgap: 0.75rem 1.25rem;andmargin-top: 10px;withmargin-top: 0.625rem;.
Suggested patch
<script setup lang="ts">
import { onMounted, ref } from 'vue'
+import { useI18n } from 'vue-i18n'
const isLoaded = ref(false)
+const { t } = useI18n()
onMounted(() => {
setTimeout(() => {
isLoaded.value = true
@@
<a
href="https://docs.projectbluefin.io/blog/making-our-own-fate/"
target="_blank"
rel="noopener noreferrer"
- >Alpha 2 Announcement →</a>
+ >{{ t('DakotaScene.Release.Alpha2Announcement') }}</a>
<a
href="https://docs.projectbluefin.io/blog/dakota-alpha-1/"
target="_blank"
rel="noopener noreferrer"
- >Alpha 1 Announcement →</a>
+ >{{ t('DakotaScene.Release.Alpha1Announcement') }}</a>
</div>
.release-links {
display: flex;
flex-wrap: wrap;
- gap: 12px 20px;
- margin-top: 10px;
+ gap: 0.75rem 1.25rem;
+ margin-top: 0.625rem;📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| <div class="release-links"> | |
| <a | |
| href="https://docs.projectbluefin.io/blog/making-our-own-fate/" | |
| target="_blank" | |
| rel="noopener noreferrer" | |
| >Alpha 2 Announcement →</a> | |
| <a | |
| href="https://docs.projectbluefin.io/blog/dakota-alpha-1/" | |
| target="_blank" | |
| rel="noopener noreferrer" | |
| >Alpha 1 Announcement →</a> | |
| </div> | |
| <div class="release-links"> | |
| <a | |
| href="https://docs.projectbluefin.io/blog/making-our-own-fate/" | |
| target="_blank" | |
| rel="noopener noreferrer" | |
| >{{ t('DakotaScene.Release.Alpha2Announcement') }}</a> | |
| <a | |
| href="https://docs.projectbluefin.io/blog/dakota-alpha-1/" | |
| target="_blank" | |
| rel="noopener noreferrer" | |
| >{{ t('DakotaScene.Release.Alpha1Announcement') }}</a> | |
| </div> |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@src/components/dakota/DakotaScene.vue` around lines 37 - 48, In
DakotaScene.vue replace the hardcoded anchor labels "Alpha 2 Announcement →" and
"Alpha 1 Announcement →" with i18n lookups (e.g. use this.$t or $t in the
template like {{ $t('dakota.alpha2Announcement') }} and {{
$t('dakota.alpha1Announcement') }} and add corresponding keys in your locale
files), and update the .release-links CSS rules to use rem units by changing
gap: 12px 20px; to gap: 0.75rem 1.25rem; and margin-top: 10px; to margin-top:
0.625rem; so the component (DakotaScene and its .release-links class) uses
localized text and rem-based spacing.
| .release-links { | ||
| display: flex; | ||
| flex-wrap: wrap; | ||
| gap: 12px 20px; | ||
| margin-top: 10px; | ||
|
|
There was a problem hiding this comment.
Avoid new hardcoded pixel spacing values in this block.
This introduces px spacing in changed SCSS; switch to rem/tokenized sizing.
Suggested patch
.release-links {
display: flex;
flex-wrap: wrap;
- gap: 12px 20px;
- margin-top: 10px;
+ gap: 0.75rem 1.25rem;
+ margin-top: 0.625rem;As per coding guidelines, “Do not hardcode pixel sizes; use TailwindCSS utilities for responsive sizing”.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| .release-links { | |
| display: flex; | |
| flex-wrap: wrap; | |
| gap: 12px 20px; | |
| margin-top: 10px; | |
| .release-links { | |
| display: flex; | |
| flex-wrap: wrap; | |
| gap: 0.75rem 1.25rem; | |
| margin-top: 0.625rem; | |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@src/components/dakota/DakotaScene.vue` around lines 138 - 143, The
.release-links CSS uses hardcoded pixel values (gap: 12px 20px; margin-top:
10px) which violates the no-px rule; replace these with tokenized/rem or
Tailwind spacing utilities: convert gap and margin-top to equivalent rem/token
values or use Tailwind classes (e.g., gap-x-? gap-y-? and mt-?) instead,
updating the .release-links usage in DakotaScene.vue (and any template markup)
so spacing comes from design tokens/Tailwind rather than explicit px values.
Summary
latesttoalpha2:dakota-live-alpha2.iso/dakota-nvidia-live-alpha2.isoTest plan
npm run build✓npm run lint:fix✓Summary by CodeRabbit