It does build and run. It was mostly guesswork though as my JS is not a thing.
Migrate to Astro v4 #449
Preview ready: https://forgejo.codeberg.page/@pull_449/
https://forgejo.codeberg.page/@pull_449/docs/v7.0/admin/command-line/
https://forgejo.codeberg.page/@pull_449/docs/next/admin/command-line/
https://forgejo.codeberg.page/@pull_449/docs/latest/admin/command-line/
https://forgejo.codeberg.page/@pull_449/docs/v1.21/admin/command-line/
https://forgejo.codeberg.page/@pull_449/docs/v7.0/admin/actions/
Downgrade to marked is because they added async which breaks rss:
src/pages/rss.xml.ts:23:26 - error TS2345: Argument of type 'string | Promise<string>' is not assignable to parameter of type 'string'.
Type 'Promise<string>' is not assignable to type 'string'.
23 content: sanitizeHtml(marked.parse(post.body)),
~~~~~~~~~~~~~~~~~~~~~~~
No idea how to fix that and even if async gets disabled TS won't recognize that it's never a Promise.
I THINK it works, only bugged thing is rss part which hasn't displayed anything. Not sure why though.
Edit:
Changed back to wip so it won't get merged by accident before a proper review
changed hook to go through bash per https://github.com/lint-staged/lint-staged/issues/825#issuecomment-674575655
this also solves pnpm lock migration
I browsed preview for a few minutes and it seems to work fine, I could not find any new bugs. I'm not competent to approve this.
Looks good, thank for the hard work! I only found one regression.
Once fixed, I would recommend not waiting too long and merging it (and fixing other bugs afterwards).
@ -50,1 +54,4 @@
rehypePlugins: [rehypeSlug, [rehypeAutolinkHeadings, autolinkOptions]],
shikiConfig: {
langs: [caddyFileLang],
},
(削除) The syntax coloration does not work https://forgejo.codeberg.page/@pull_449/docs/latest/admin/reverse-proxy/ (削除ここまで)
This is because this PR is not on the top of origin/main, never mind.
@ -12,3 +12,3 @@
<button type="button" class={className} aria-label={label} data-aw-toggle-menu>
<Icon name={iconName} class={iconClass} optimize={false} />
<Icon name={iconName} class={iconClass} />
Fix:
---
const {
label = 'Toggle Menu',
class:
className = 'ml-1.5 text-zinc-500 dark:text-zinc-400 hover:bg-steel-100 dark:hover:bg-steel-800 focus:outline-none focus:ring-4 focus:ring-gray-200 dark:focus:ring-gray-700 rounded-lg text-sm p-2.5 inline-flex items-center transition',
} = Astro.props;
// manual copy/paste of the tabler:menu icon to allow edition via CSS [data-aw-toggle-menu] when toggled
---
<button type="button" class={className} aria-label={label} data-aw-toggle-menu>
<svg
xmlns="http://www.w3.org/2000/svg"
xmlns:xlink="http://www.w3.org/1999/xlink"
preserveAspectRatio="xMidYMid meet"
viewBox="0 0 24 24"
class="w-6 h-6"
astro-icon="tabler:menu"
><g
class="icon-tabler"
fill="none"
stroke="currentColor"
stroke-width="2"
stroke-linecap="round"
stroke-linejoin="round"><path d="M4 8h16"></path><path d="M4 16h16"></path></g
></svg>
</button>
rename style to match newer syntax
I advise to merge this pull request only after making sure at least one person has plenty of time in the days that follow to deal with the unexpected consequences.
@thefox do you have some time in the coming days/weeks?
I can make myself available to help with this risky transition.
Sure, I have time.
Backup would be very much appreciated :)
The website is luckily not that complex. What about making a checklist of all that should be manually tested? I would go over it on the preview to help with that. I don't understand how to fix issues but I can report a broken item in the checklist 😁. Such a checklist should also take into account the fact that the docs are included as a submodule, in case that matters.
Checklist draft (should ideally be put into a md file into the repo):
- Note that ideally both the mobile (narrow) and desktop (wide) versions should be tested
- visit the homepage
- visit the
rss.xmlfeed (⚠️the menu button points to themainversion: put the URL manually) - switch the theme (light/dark)
- visit the FAQ
- visit the Releases page (there should be one
Stableand oneOld Stabletag) - visit the News page
- visit the News page for a given tag (
reportfor instance) - visit the first News
- visit the docs
/latest - visit the docs
/next - visit the docs > Admin > Reverse proxy and check that all blocks except 2 have syntax coloring (currently not the case here, because the PR is not up-to-date)
- visit the docs > Admin > Configuration Cheat Sheet and check that the internal page navigation (on the right) behaves correctly (independently scrollable / click on item goes to the right place) only available on desktop for now
Checklist draft (should ideally be put into a md file into the repo):
- Note that ideally both the mobile (narrow) and desktop (wide) versions should be tested
- visit the homepage
- visit the
rss.xmlfeed (⚠️the menu button points to themainversion: put the URL manually)- switch the theme (light/dark)
- visit the FAQ
- visit the Releases page (there should be one
Stableand oneOld Stabletag)- visit the News page
- visit the News page for a given tag (
reportfor instance)- visit the first News
- visit the docs
/latest- visit the docs
/next- visit the docs > Admin > Reverse proxy and check that all blocks except 2 have syntax coloring (currently not the case here, because the PR is not up-to-date)
- visit the docs > Admin > Configuration Cheat Sheet and check that the internal page navigation (on the right) behaves correctly (independently scrollable / click on item goes to the right place) only available on desktop for now
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?