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

Build and publish an unstable explorer version #2181

Merged
merged 5 commits into from
Dec 17, 2024
Merged

Conversation

Alenar
Copy link
Collaborator

@Alenar Alenar commented Dec 16, 2024

Content

This PR add a 'Unstable' feature flag to the explorer, toggled by setting a UNSTABLE environment variable to 1 at compile time.
This, alongside another change that allow to parametrize the explorer base path (to have correct intra links), allow us to have two published version of the explorer:

  • https://mithril.network/explorer/: that will use the packaged version of the explorer from the last stable release, built with unstable feature disabled ( ⚒️ coming soon, see comments).
  • https://mithril.network/explorer/unstable: that will use the latest code from the main branch, build with unstable features enabled.

Pre-submit checklist

  • Branch
    • Crates versions are updated (if relevant)
    • CHANGELOG file is updated (if relevant)
    • Commit sequence broadly makes sense
    • Key commits have useful messages
  • PR
    • No clippy warnings in the CI
    • Self-reviewed the diff
    • Useful pull request description
    • Reviewer requested
  • Documentation
    • Update README file (if relevant)
    • Update documentation website (if relevant)
    • Add dev blog post (if relevant)

Comments

This does not finish #2172 as we need to wait for a new release to have a packaged "stable" explorer build that can be retrieved each time we publish to github pages.
In the meantime we will keep using the main branch code for the published "stable" version but with the unstable features disabled.

Issue(s)

Relates to #2172

@Alenar Alenar self-assigned this Dec 16, 2024
@Alenar Alenar force-pushed the djo/2172/unstable-explorer branch from 61730fb to d7d7789 Compare December 16, 2024 18:09
Copy link

github-actions bot commented Dec 16, 2024

Test Results

    4 files  ±0     52 suites  ±0   9m 47s ⏱️ -3s
1 428 tests ±0  1 428 ✅ ±0  0 💤 ±0  0 ❌ ±0 
1 639 runs  ±0  1 639 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 52b7107. ± Comparison against base commit 461e086.

♻️ This comment has been updated with latest results.

Copy link
Collaborator

@sfauvel sfauvel left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Member

@jpraynaud jpraynaud left a comment

Choose a reason for hiding this comment

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

LGTM 👍

CHANGELOG.md Outdated Show resolved Hide resolved
Copy link
Collaborator

@dlachaume dlachaume left a comment

Choose a reason for hiding this comment

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

LGTM 🚀

That can be toogled on by setting a `UNSTABLE` environment variable to
`1` when building developer or production builds.
Using a `BASE_PATH` env var.

Reminder: the base path is notably added to all intra-links generated by
the router.
@Alenar Alenar force-pushed the djo/2172/unstable-explorer branch from d7d7789 to 52b7107 Compare December 17, 2024 14:20
@Alenar Alenar temporarily deployed to testing-preview December 17, 2024 14:31 — with GitHub Actions Inactive
@Alenar Alenar temporarily deployed to testing-sanchonet December 17, 2024 14:31 — with GitHub Actions Inactive
@Alenar Alenar merged commit 06e7e43 into main Dec 17, 2024
51 of 54 checks passed
@Alenar Alenar deleted the djo/2172/unstable-explorer branch December 17, 2024 15:10
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.

4 participants