Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Toolkit: announce availability of new version #297

Closed
eladb opened this issue Jul 10, 2018 · 0 comments · Fixed by #2484 or MechanicalRock/tech-radar#14 · May be fixed by MechanicalRock/cdk-constructs#5, MechanicalRock/cdk-constructs#6 or MechanicalRock/cdk-constructs#7
Labels
ops-excellence Operational Excellence p1 package/tools Related to AWS CDK Tools or CLI

Comments

@eladb
Copy link
Contributor

eladb commented Jul 10, 2018

The toolkit should check if we released a new version and announce it to users upon first invocation

@eladb eladb added the ops-excellence Operational Excellence label Jul 10, 2018
@debora-ito debora-ito added the package/tools Related to AWS CDK Tools or CLI label Nov 7, 2018
@fulghum fulghum added the p1 label Mar 6, 2019
rix0rrr pushed a commit that referenced this issue May 10, 2019
Check, once a day, if a newer CDK version available in npm and announce
it's availability at the end of a significant command.

TESTING:
* New unit tests for version.ts
* Downgraded version number in package.json and verified that the
  expected message is printed.
* Verified that the file cache throttles the check to run only once per
  day.

Closes #297
SanderKnape pushed a commit to SanderKnape/aws-cdk that referenced this issue May 14, 2019
Check, once a day, if a newer CDK version available in npm and announce
it's availability at the end of a significant command.

TESTING:
* New unit tests for version.ts
* Downgraded version number in package.json and verified that the
  expected message is printed.
* Verified that the file cache throttles the check to run only once per
  day.

Closes aws#297
This was referenced Dec 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment