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

Add module field #5594

Merged
merged 1 commit into from
Nov 5, 2019
Merged

Add module field #5594

merged 1 commit into from
Nov 5, 2019

Conversation

rslawik
Copy link
Contributor

@rslawik rslawik commented Oct 4, 2019

Copy link
Contributor

@justinfagnani justinfagnani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch. Can you update the CHANGELOG?

@justinfagnani
Copy link
Contributor

@azakus @kevinpschaaf how do we maintain the CHANGELOG in Polymer? Is it generated or updated by hand?

@kevinpschaaf
Copy link
Member

Yeah, the changelog in the polymer repro predates when we made changelogs per PR; we run a script at release time to gather the commit log.

@rslawik
Copy link
Contributor Author

rslawik commented Oct 13, 2019

If the changelog is updated automatically, can we merge this PR in?

@rslawik
Copy link
Contributor Author

rslawik commented Nov 1, 2019

Ping. It seems that the CHANGELOG update is not a blocker to merge this.
@justinfagnani @azakus

Once merged, when is it expected to be published to npm?

Copy link
Member

@kevinpschaaf kevinpschaaf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, confirmed this is already what we do in LitElement

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants