Update weather extension

[jenningsb2]

Description

Adds a Temperature dropdown preference to the Weather Menu Bar command with two options: Actual (default, current behavior) and Feels Like. When set to Feels Like, the menu bar text shows the feels-like temperature instead of the actual temperature. Falls back to the actual temperature if the feels-like value is unavailable.

The dropdown menu contents are unchanged and still show both the Temperature and Feels Like rows.

Screencast

Straightforward preference change. With Feels Like selected the menu bar reads e.g. 74 °F while the Temperature row in the dropdown still shows 70 °F.

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used in the README are located outside the metadata folder if they were not generated with our metadata tool

🤖 Generated with Claude Code

https://claude.ai/code/session_01DLRG5JDNtaAxs472tCRmTY

[raycastbot]

Thank you for your contribution! 🎉

🔔 @tonka3000 @xilopaint @ridemountainpig @spencer-michaels you might want to have a look.

You can use this guide to learn how to check out the Pull Request locally in order to test it.

📋 Quick checkout commands

BRANCH="weather-feels-like-menubar"
FORK_URL="https://github.com/jenningsb2/raycast-extensions.git"
EXTENSION_NAME="weather"
REPO_NAME="raycast-extensions"

git clone -n --depth=1 --filter=tree:0 -b $BRANCH $FORK_URL
cd $REPO_NAME
git sparse-checkout set --no-cone "extensions/$EXTENSION_NAME"
git checkout
cd "extensions/$EXTENSION_NAME"
npm install && npm run dev

We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 15 business days.

[greptile-apps]

Greptile Summary

The PR adds a menu-bar preference for displaying either the actual or feels-like temperature and updates weather-value handling to support the fallback behavior.

• Adds Actual and Feels Like options to the menu-bar command preferences.
• Selects the configured temperature while preserving the existing dropdown details.
• Returns no feels-like value when the API field is unavailable, allowing fallback to the actual temperature.
• Updates extension dependencies, authorship metadata, and the changelog.

Confidence Score: 4/5

The functional change appears sound, but the changelog placeholder requirement must be restored before merging.

The previous feels-like fallback defect is fully fixed because missing values now return before formatting, allowing the actual temperature fallback to run. The remaining issue is the explicit repository requirement that new changelog headings retain {PR_MERGE_DATE}.

Files Needing Attention: extensions/weather/CHANGELOG.md

Important Files Changed

Filename	Overview
extensions/weather/src/menubar.tsx	Selects the configured menu-bar temperature and correctly falls back to the actual value.
extensions/weather/src/wttr.ts	Avoids formatting absent feels-like fields, fully addressing the previous malformed fallback finding.
extensions/weather/package.json	Adds the menu temperature preference, author metadata, and an esbuild override.
extensions/weather/package-lock.json	Refreshes the dependency lockfile consistently with the manifest changes.
extensions/weather/CHANGELOG.md	Documents the feature but uses a literal date instead of the required merge-date placeholder.

Prompt To Fix All With AI

### Issue 1
extensions/weather/CHANGELOG.md:3
**Literal Changelog Date**

This heading uses `2026-09-08` instead of the required `{PR_MERGE_DATE}` placeholder. Repository rules require new changelog headings to keep this placeholder so the merge date can be populated automatically; this requirement must be satisfied before merging.

```suggestion
## [Feels Like in Menu Bar] - {PR_MERGE_DATE}
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (3): Last reviewed commit: "Update CHANGELOG.md" | Re-trigger Greptile}

[greptile-apps]

Broken Feels-Like Fallback

When current conditions exist but the selected FeelsLikeC or FeelsLikeF field is unavailable, getCurrentFeelLikeTemperature produces a truthy string such as "undefined °C". Therefore, feelsLike || temp does not use the actual temperature fallback and instead displays malformed menu-bar text.

Suggested change

	const feelsLike = getCurrentFeelLikeTemperature(curcon)?.valueAndUnit;
	const menuTemp = menutemperature === "feelslike" ? feelsLike || temp : temp;
	const feelsLike = getCurrentFeelLikeTemperature(curcon);
	const menuTemp = menutemperature === "feelslike" ? (feelsLike?.value ? feelsLike.valueAndUnit : temp) : temp;

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/weather/src/menubar.tsx
Line: 408-409

Comment:
**Broken Feels-Like Fallback**

When current conditions exist but the selected `FeelsLikeC` or `FeelsLikeF` field is unavailable, `getCurrentFeelLikeTemperature` produces a truthy string such as `"undefined °C"`. Therefore, `feelsLike || temp` does not use the actual temperature fallback and instead displays malformed menu-bar text.

```suggestion
  const feelsLike = getCurrentFeelLikeTemperature(curcon);
  const menuTemp = menutemperature === "feelslike" ? (feelsLike?.value ? feelsLike.valueAndUnit : temp) : temp;
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

[pernielsentikaer]

Looks good to me, approved 🔥

[github-actions]

Published to the Raycast Store:
https://raycast.com/tonka3000/weather

[raycastbot]

🎉 🎉 🎉

We've rewarded your Raycast account with some credits. You will soon be able to exchange them for some swag.

[greptile-apps]

Literal Changelog Date

This heading uses 2026-09-08 instead of the required {PR_MERGE_DATE} placeholder. Repository rules require new changelog headings to keep this placeholder so the merge date can be populated automatically; this requirement must be satisfied before merging.

Suggested change

	## [Feels Like in Menu Bar] - 2026-09-08
	## [Feels Like in Menu Bar] - {PR_MERGE_DATE}

Rule Used: What: Changelog entries must use {PR_MERGE_DATE}... (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/weather/CHANGELOG.md
Line: 3

Comment:
**Literal Changelog Date**

This heading uses `2026-09-08` instead of the required `{PR_MERGE_DATE}` placeholder. Repository rules require new changelog headings to keep this placeholder so the merge date can be populated automatically; this requirement must be satisfied before merging.

```suggestion
## [Feels Like in Menu Bar] - {PR_MERGE_DATE}
```

**Rule Used:** What: Changelog entries must use `{PR_MERGE_DATE}`... ([source](https://app.greptile.com/raycast/-/custom-context?memory=c2214c11-df56-490a-b1c0-09a385df481a))

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.