unkeyed
[🕹️] API Name is cached after renaming
Preliminary Checks
-
[X] I have reviewed the documentation: https://unkey.com/docs
-
[X] I have searched for existing issues: https://github.com/unkeyed/unkey/issues
-
[X] This issue is not a question, general help request, or anything other than a bug report directly related to Unkey. Please ask questions in our Discord community: https://unkey.com/discord.
Reproduction / Replay Link (Optional)
No response
Issue Summary
Sometimes when you rename your api the old name will stayed cached in the header
Steps to Reproduce
- Go into an api
- Rename it
- See if the name is correct, sometimes this only happens after a second rename ( See repro video on prod )
Expected behavior
That the name always changes once I press save
Other information
No response
Screenshots
https://github.com/user-attachments/assets/5321c0d8-e705-4b48-a628-a66626334f1e
Version info
-
![linear[bot] avatar](https://avatars.githubusercontent.com/in/20150?v=4 "Published by a pub.dev verified publisher"){kind=small}
When using unstable_cache in Breadcrum to cache API calls, changes to properties are not triggering cache revalidation. Specifically, updating a property does not invalidate the cached response, resulting in stale data being returned.
Not only in api renaming but also -
- API renaming
- Rate limiting namespace updates
- Authorization role updates ( changing role names)
- Authorization permission updates (changing permission names
To address this, we can revalidateTag to revalidate the cache when properties change.
one of solutions - https://github.com/user-attachments/assets/a5b08387-9628-44de-82b3-443588256f69
I have working solution but waiting for maintainers to add oss.gg label
Hey @AkshayBandi027 You should first assign yourself and then start working on it. But before that, pls wait for the maintainers to add oss.gg label and points
@AkshayBandi027 Yes, I was about to suggest tags as well, can you do them all?
![oss-gg[bot] avatar](https://avatars.githubusercontent.com/in/835270?v=4 "Published by a pub.dev verified publisher"){kind=small}
Assigned to @Harsh-Sanklecha! Please open a draft PR linking this issue within 48h ⚠️ If we can't detect a PR from you linking this issue in 48h, you'll be unassigned automatically 🕹️ Excited to have you ship this 🚀
@Harsh-Sanklecha hold on please, there's already a PR for this I'm trying to understand why the bot allowed it
@Harsh-Sanklecha, Just a little reminder: Please open a draft PR linking this issue within 12 hours. If we can't detect a PR in 12h, you will be unassigned automatically.
