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

Remove version #1410

Merged
merged 13 commits into from
Mar 6, 2024
Merged

Remove version #1410

merged 13 commits into from
Mar 6, 2024

Conversation

adamgall
Copy link
Member

@adamgall adamgall commented Mar 6, 2024

Closes #1409

This PR does a couple of things:

  1. Visual - changes the "version" identifier in the footer of the landing page from the version defined in package.json to the git shorthash of the current build.
  2. Operational - removes the RELEASES.md doc, which is out of date and not relevant or in line with where I'm trying to move our release process to.
  3. Developer experience - Cleaned up the scripts in package.json. Removed a few that (I don't think) anyone uses. Fixed some bugs in others.

Copy link

netlify bot commented Mar 6, 2024

Deploy Preview for fractal-framework-dev ready!

Name Link
🔨 Latest commit 6cfbe66
🔍 Latest deploy log https://app.netlify.com/sites/fractal-framework-dev/deploys/65e8c624f3113e000721e304
😎 Deploy Preview https://deploy-preview-1410.app.dev.fractalframework.xyz
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@adamgall adamgall self-assigned this Mar 6, 2024
"build": "npm run graphql:build && NEXT_PUBLIC_GIT_HASH=`git rev-parse HEAD` next build",
"build:windows": "for /F \"delims=\" %I in ('git rev-parse HEAD') do set \"NEXT_PUBLIC_GIT_HASH=%I\" && next build",
Copy link
Member Author

Choose a reason for hiding this comment

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

Removed this, none of us are on Windows

"dev": "npm run set:env & next dev",
"start": "npm run set:env & next start",
"start:https": "npm run set:env & HTTPS=true next start",
"start:windows": "set \"GENERATE_SOURCEMAP=false\" && for /F \"delims=\" %I in ('git rev-parse HEAD') do set \"NEXT_PUBLIC_GIT_HASH=%I\" && next start",
Copy link
Member Author

@adamgall adamgall Mar 6, 2024

Choose a reason for hiding this comment

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

Removed this, none of us are on Windows.

Edit: this comment only applies to line 60.

Comment on lines -58 to -59
"start": "npm run set:env & next start",
"start:https": "npm run set:env & HTTPS=true next start",
Copy link
Member Author

Choose a reason for hiding this comment

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

I removed these, and these two scripts are what I'm most unsure about. When/who is ever running these start scripts?

Copy link
Contributor

Choose a reason for hiding this comment

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

I do technically use start locally as I do like to test on the build.

Copy link
Member Author

Choose a reason for hiding this comment

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

heard! I will replace these.

Copy link
Contributor

Choose a reason for hiding this comment

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

start also used by Netlify to run production server

Copy link
Member Author

Choose a reason for hiding this comment

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

@mudrila are you sure about that? I see that netlify builds the site with npm run build

Screenshot 2024-03-06 at 1 16 54 PM

but I don't see anywhere in the settings where the start script is executed...

Copy link
Member Author

Choose a reason for hiding this comment

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

@mudrila as a test, I just removed the start and start:https scripts from package.json again, and the deploy preview for this PR builds and deploys just fine.

Copy link
Member Author

Choose a reason for hiding this comment

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

ok, adding the start script back even tho it's just next start

@@ -53,13 +52,8 @@
"scripts": {
"lint": "next lint",
"lint:fix": "next lint --fix",
"set:env": "GENERATE_SOURCEMAP=false NEXT_PUBLIC_GIT_HASH=`git rev-parse HEAD`",
Copy link
Member Author

@adamgall adamgall Mar 6, 2024

Choose a reason for hiding this comment

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

Removed this script and inlined the important part (NEXT_PUBLIC_GIT_HASH=git rev-parse HEAD) into the dev script. Removed GENERATE_SOURCEMAP=false because that was a CRA thing, not really relevant in our current project.

}
textStyle="text-sm-mono-bold"
>
{process.env.NEXT_PUBLIC_GIT_HASH.substring(0, 7)}
Copy link
Member Author

Choose a reason for hiding this comment

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

The only real change here is that I'm showing a the git shorthash as the version identifier.

@adamgall adamgall merged commit e229bb0 into develop Mar 6, 2024
5 checks passed
@adamgall adamgall deleted the remove-version branch March 6, 2024 21:57
@adamgall adamgall mentioned this pull request Mar 7, 2024
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.

Remove Semantic Versioning from the interface
3 participants