You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "charpeni (via GitHub)" <gi...@apache.org> on 2023/04/18 23:21:24 UTC

[GitHub] [superset] charpeni commented on a diff in pull request #23730: chore: add npm publish steps to release/readme

charpeni commented on code in PR #23730:
URL: https://github.com/apache/superset/pull/23730#discussion_r1170658241


##########
RELEASING/README.md:
##########
@@ -486,3 +486,18 @@ click the 3-dot icon and select `Create Release`, paste the content of the ANNOU
 release notes, and publish the new release.
 
 At this point, a GitHub action will run that will check whether this release's version number is higher than the current 'latest' release. If that condition is true, this release sha will automatically be tagged as `latest` so that the most recent release can be referenced simply by using the 'latest' tag instead of looking up the version number. The existing version number tag will still exist, and can also be used for reference.
+
+### Npm Release
+You might want to publish the latest @superset-ui release to npm
+```bash
+cd superset/superset-front

Review Comment:
   Should it be:
   
   ```suggestion
   cd superset/superset-frontend
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org