aws-amplify / aws-amplify/amplify-cli
Rate limited when attempting to upgrade Amplify CLI
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 825
- Avg merge
- 11d 23h
- Merged PRs (30d)
- 2
Description
### How did you install the Amplify CLI?
npm -g i @aws-amplify/cli
### If applicable, what version of Node.js are you using?
v16.13.0
### Amplify CLI Version
10.6.0
### What operating system are you using?
Windows
### Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
### Describe the bug

### Expected behavior
Amplify package upgrades to the latest version
### Reproduction steps
1. Have 10.6.0 installed
2. run `amplify upgrade`
3. profit?
### Project Identifier
_No response_
### Log output
```
# Put your logs below this line
```
### Additional information
_No response_
### Before submitting, please confirm:
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.
Contributor guide
Research direction
Start by reproducing `amplify upgrade` from Amplify CLI 10.6.0 on Windows with Node.js v16.13.0, using the global npm installation described in the issue. Inspect the rate-limit error and the CLI upgrade path; done means the command upgrades to the latest package without triggering the reported rate limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100