[Bug]: eap / rc bucket for a program may contain outdated version

[k0pernikus]

Prerequisites

• I have written a descriptive issue title.
• I have searched all issues/PRs to ensure it has not already been reported or fixed.
• I have verified that I am using the latest version of Scoop and corresponding bucket.

Package Name

phpstorm-eap

Expected/Current Behaviour

Affected version buckets:

• phpstorm-eap
• phpstorm-rc

Also affected but extras bucket:

• phpstorm

I have installed phpstorm via phpstorm-eap. I was confused why I didn't get the latest build (2025.3-253.28294.345) but remained on 2025.3-253.28294.163.

When searching for phpstorm on scoop, I got this listing:

scoop search phpstorm
Results from local buckets...

Name         Version              Source   Binaries
----         -------              ------   --------
phpstorm     2025.3-253.28294.345 extras
phpstorm-eap 2025.3-253.28294.163 versions
phpstorm-rc  2025.3-253.28294.257 versions

This leads to the odd behavior that both the phpstorm-eap and phpstorm-rc buckets provide different outdated versions than the "normal" extras bucket. My expectation of the versions is:

phpstorm-eap >= phpstorm-rc >= phpstorm

(and in this situation this is completly reversed with phpstorm-eap < phpstorm-rc < phpstorm)

I understand why this is happening: 2025.3-253.28294.163 was the latest EAP (early access version), and the next update was a RC (release candidate), and the next version was a normal release -- so it is /technically/ true that those older version are the most up to date version as a eap and rc version, yet from a user perspective it makes no sense as I was using the phpstorm-eap bucket to always get the latest release in the first place.

I always want the most current version installed.

Steps to Reproduce

scoop search phpstorm
Results from local buckets...

Name         Version              Source   Binaries
----         -------              ------   --------
phpstorm     2025.3-253.28294.345 extras
phpstorm-eap 2025.3-253.28294.163 versions
phpstorm-rc  2025.3-253.28294.257 versions

Possible Solution

I am not entirely sure if and how you want to reflect that issue or if you consider this as something a user may have to manually resolve.. As a suggestion it would be really nice to have another channel like phpstorm-latest that would point to always the most up to date version of phpstorm, no matter if released through the normal extras bucket (phpstorm), or the two versions buckets (phpstorm-eap, phpstorm-rc).

I opened this ticket for phpstorm, yet other Jetbrains IDE / products may be affected as well as they have the same release pattern of eap, rc, and normal versions.

I am not sure if other tools release through the versions bucket would also be affected, yet I think it may be likely.

Scoop and Buckets Version

scoop --version
Current Scoop version:
b588a06e (HEAD -> master, tag: v0.5.3, origin/master, origin/HEAD) chore(release): Bump to version 0.5.3 (resync) (#6436)

'main' bucket:
c185fd9e57 (HEAD -> master, origin/master, origin/HEAD) prek: Update to version 0.2.21

'extras' bucket:
88d5336456 (HEAD -> master, origin/master, origin/HEAD) ungoogled-chromium: Update to version 143.0.7499.40-1.1

'versions' bucket:
17e4db58d4 (HEAD -> master, origin/master, origin/HEAD) zed-opengl-nightly: Update to version 2025-12-09

'nerd-fonts' bucket:
10f08d16 (HEAD -> master, origin/master, origin/HEAD) LXGWNeoZhiSong: Update to version 1.053

Scoop Config

scoop config

last_update              scoop_repo                              scoop_branch aria2-enabled
-----------              ----------                              ------------ -------------
Tue, 2025-12-09 12:48:13 https://github.com/ScoopInstaller/Scoop master                True

PowerShell Version

$PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.26100.7019
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.26100.7019
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Additional Softwares

No response

[z-Fng]

I am not entirely sure if and how you want to reflect that issue or if you consider this as something a user may have to manually resolve.

We assume that users choosing the EAP version intend to stay on EAP. Unless the upstream explicitly publishes a version as an EAP build, we cannot guarantee that an EAP build will always be newer than the stable release.

I always want the most current version installed.

As a suggestion it would be really nice to have another channel like phpstorm-latest that would point to always the most up to date version of phpstorm, no matter if released through the normal extras bucket (phpstorm), or the two versions buckets (phpstorm-eap, phpstorm-rc).

Adding the corresponding <app>-latest manifest is the preferred approach, and similar manifests already exist, such as phpstorm-latest. If you'd like, please follow the Contributing Guide, and feel free to open a pull request for this.

Versions/bucket/phpstorm-latest.json

Lines 40 to 56 in 7fa1ee6

	"script": [
	"$productCode = 'PS'",
	"$releaseURLs = @(",
	" ('https://data.services.jetbrains.com/products/releases?code={0}&latest=true&platform=zip&type=eap' -f $productCode),",
	" ('https://data.services.jetbrains.com/products/releases?code={0}&latest=true&platform=zip&type=rc' -f $productCode),",
	" ('https://data.services.jetbrains.com/products/releases?code={0}&latest=true&platform=zip&type=release' -f $productCode)",
	")",
	"$latestRelease = $ReleaseURLs | ForEach-Object {",
	" $url = $_",
	" $response = Invoke-RestMethod -Uri $url -UseBasicParsing",
	" [PSCustomObject]@{",
	" version = ($response.$productCode)[0].majorVersion",
	" build = ($response.$productCode)[0].build",
	" }",
	"} | Sort-Object {[version]$_.build} -Descending | Select-Object -First 1",
	"Write-Output \"$($latestRelease.version)-$($latestRelease.build)\""
	],

[z-Fng]

phpstorm-latest has already been added to the Versions bucket in PR #1122.

[k0pernikus]

phpstorm-latest has already been added to the Versions bucket in PR #1122.

Can confirm that latest exists:

Name            Version               Source   Binaries
----            -------               ------   --------
phpstorm        2025.3-253.28294.345  extras
phpstorm-eap    2025.3-253.28294.163  versions
phpstorm-latest 2025.3-253.29346.44   versions
phpstorm-rc     2025.3.1-253.29346.44 versions

I was confused that it didn't pop up at first, yet I needed to run scoop update prior.

---

Other Jetbrains IDE don't have the latest bucket yet, shall I create an issue for each?

---

E.g. pycharm:

Name                     Version               Source   Binaries
----                     -------               ------   --------
pycharm-professional     2025.3-253.28294.336  extras
pycharm                  2025.3-253.28294.336  extras
pycharm-eap              2025.2-252.23892.194  versions
pycharm-professional-eap 2025.3-253.28294.166  versions
pycharm-professional-rc  2025.3.1-253.29346.46 versions
pycharm-rc               2025.2.3-252.26830.27 versions

---

or goland:

scoop search goland
Results from local buckets...

Name       Version              Source   Binaries
----       -------              ------   --------
goland     2025.3-253.28294.337 extras
goland-eap 2025.3-253.28294.175 versions
goland-rc  2025.3-253.28294.249 versions

---

scoop search rider
Results from local buckets...

Name Version Source Binaries

---

rider 2025.3.0.4-253.28294.356 extras
rider-eap 2025.3-EAP8-253.28086.30 versions

etc. pp.

---

Just notice that some pull requests already exist:

pycharm-professional-latest : add version 231.8109.140 #1119
clion-latest : add version 231.8770.66 #1197
rubymine-latest : add version 232.6095.8 #1222

[z-Fng]

Other Jetbrains IDE don't have the latest bucket yet, shall I create an issue for each?

No need to create any more issues. If you'd like, feel free to submit PRs. I'll add the rest in a few days.