Skip to content

Conversation

@connorjclark
Copy link
Collaborator

@connorjclark connorjclark requested a review from a team as a code owner December 9, 2020 04:05
@connorjclark connorjclark requested review from Beytoven and removed request for a team December 9, 2020 04:05
@google-cla google-cla bot added the cla: yes label Dec 9, 2020
Copy link
Collaborator

@patrickhulce patrickhulce left a comment

Choose a reason for hiding this comment

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

amazing 😍

- run: yarn

- name: bash $GITHUB_WORKSPACE/.github/scripts/bump-nightly-version.sh
- uses: JS-DevTools/npm-publish@v1
Copy link
Collaborator

Choose a reason for hiding this comment

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

I believe we want to peg to a specific hash since the tag can be changed at any time

Copy link
Collaborator

Choose a reason for hiding this comment

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

aside: do we actually need this? it seems like we don't use any of their touted improvements over just npm publish and if we can avoid giving out our NPM_TOKEN with a line or two, that feels worth it :)

Copy link
Collaborator Author

@connorjclark connorjclark Dec 9, 2020

Choose a reason for hiding this comment

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

Only publishes if the version number in package.json differs from the latest on NPM

hmm..does npm even let you republish the latest/any version?

Copy link
Collaborator

Choose a reason for hiding this comment

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

not that I'm aware of. but also aren't we publishing a brand new version every time guaranteed?

Copy link
Member

@paulirish paulirish left a comment

Choose a reason for hiding this comment

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

seems cool but two ideas.

# Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
# Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
##
# TMP DELETE ME

This comment was marked as outdated.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

friggne actions failing


set -euxo pipefail

DATE=$(date '+%Y%m%d')
Copy link
Member

Choose a reason for hiding this comment

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

(i wrote a comment but it disappeared 😢 )

since this publishes in the morning with today's date.. it does mean that commits that land on a day (say December 9th) are not in the 1209 release.

date --date="yesterday" '+%Y%m%d'

fixes that.

also this --date flag for date is in gnu date but not bsd/mac date. so doesnt work on mac but should be fine on CI

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants