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

Changesets #28

Merged
merged 4 commits into from
Jun 1, 2016
Merged

Changesets #28

merged 4 commits into from
Jun 1, 2016

Conversation

kddnewton
Copy link
Owner

No description provided.

@mrdziuban
Copy link
Contributor

This is more of a general question, but also relates to changesets. Should we do some logic around supporting really large templates? The limits specify that a template can be 51,200 bytes, but can be up to 460,800 if it's uploaded to S3. What do you think?

@kddnewton
Copy link
Owner Author

I'd wait until we need that functionality to worry about it

@mrdziuban
Copy link
Contributor

Agreed we haven't needed it yet, but I did use S3 when making changesets for the VPC updates, so it might become relevant again for us. It would also be a good feature to have when open sourcing. I don't think we need to worry about it here though.

This could also be a minor version bump, if you want, since semver says:

"MINOR version when you add functionality in a backwards-compatible manner"

Either way, :shipit:

@kddnewton kddnewton merged commit 2a9005a into master Jun 1, 2016
@kddnewton kddnewton deleted the changesets branch June 1, 2016 20:58
kddnewton added a commit that referenced this pull request Jun 16, 2016
* support creating changesets

* bump version

* fix style warnings

* support deploying change sets
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.

None yet

2 participants