Skip to content

Conversation

@adammcodes
Copy link
Contributor

@adammcodes adammcodes commented Oct 21, 2025

Updates sprites submodule to fix typo in generation-iii/ruby-sapphire folder name (was misspelled as "ruby-saphire").

To reproduce the issue:
Currently trying to access the type sprites in generation-iii/ruby-sapphire leads to a broken path:

https://raw.githubusercontent.com/PokeAPI/sprites/master/sprites/types/generation-iii/ruby-sapphire/17.png
--> 404: Not Found

This is because of a typo in "sapphire" in the folder name: "data/v2/sprites/sprites/types/generation-iii/ruby-saphire"
"saphire" is missing a "p".

https://raw.githubusercontent.com/PokeAPI/sprites/master/sprites/types/generation-iii/ruby-saphire/17.png
--> This works.

Correct the spelling in the version group folder name to "ruby-sapphire" so that applications that use the api version group name "ruby-sapphire" to find the type sprite for generation-iii and ruby-sapphire will not lead to 404s.

@Naramsim
Copy link
Member

Thanks a lot!

@Naramsim Naramsim merged commit 4f45759 into PokeAPI:master Oct 22, 2025
2 checks passed
@pokeapi-machine-user
Copy link

A PokeAPI/api-data refresh has started. In ~45 minutes the staging branch of PokeAPI/api-data will be pushed with the new generated data.

The staging branch will be deployed in our staging environment and the entire API will be ready to review.

A Pull Request (master<-staging) will be also created at PokeAPI/api-data and assigned to the PokeAPI Core team to be reviewed. If approved and merged new data will soon be available worldwide at pokeapi.co.

@pokeapi-machine-user
Copy link

The updater script has finished its job and has now opened a Pull Request towards PokeAPI/api-data with the updated data.

The Pull Request can be seen deployed in our staging environment when CircleCI deploy will be finished (check the start time of the last build).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants