daeuniverse / daed-1 Goto Github PK

What happened

What you expect to happen

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know

Environment

• daed version (use daed --version):
• OS (e.g cat /etc/os-release):
• Kernel (e.g. uname -a):
• Others:

What happened

What you expect to happen

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know

Environment

• daed version (use daed --version):
• OS (e.g cat /etc/os-release):
• Kernel (e.g. uname -a):
• Others:

What happened

What you expect to happen

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know

Environment

• daed version (use daed --version):
• OS (e.g cat /etc/os-release):
• Kernel (e.g. uname -a):
• Others:

Context

🚀 @daebot proposed the following changelogs for release v0.2.0 generated in workflow run.

Changelogs

Features

• feat: add configure tuic modal in #157 by (@kunish)
• feat: modal reworks in #149 by (@kunish)
• feat: change icons in #147 by (@kunish)

Bug Fixes

• fix: time parsing is wrong in #171 by (@kunish)
• fix(v2ray): add missing websocket path field in #159 by (@kunish)
• fix: wan interface should be optional in #156 by (@kunish)

Others

• ci(pr-build): add ready_for_review trigger in #175 by (@yqlbu)
• chore(sync): keep upstream source up-to-date in #174 by (@daebot)
• chore: run unite tests before commiting in #172 by (@kunish)
• docs(readme): add build-status badge in #170 by (@yqlbu)
• chore: update packages in #169 by (@kunish)
• ci/fix(pr-build): skip check-run related actions based on condition in #167 by (@yqlbu)
• chore(sync): keep upstream source up-to-date in #165 by (@daebot)
• chore(sync): keep upstream source up-to-date in #164 by (@daebot)
• ci/chore(pr-build): remove unnecessary lines in #163 by (@yqlbu)
• ci(pr-build): integrate check runs to report build status in #162 by (@yqlbu)
• chore(sync): keep upstream source up-to-date in #160 by (@daebot)
• ci(build): rename Build (Stable) -> Build (Main) in #158 by (@yqlbu)
• chore(sync): keep upstream source up-to-date in #155 by (@daebot)
• ci(sync-upstream): fix invalid downstream workflow ref in #152 by (@yqlbu)
• ci(sync-upstream) apply modularity support in #151 by (@yqlbu)
• chore(pr_template): add test result section in #148 by (@yqlbu)
• ci(generate-changelogs): set dry_run to true by default in #146 by (@yqlbu)
• ci(build.yml): fix armv7 packages' architecture in #145 by (@MarksonHon)

Full Changelog: daeuniverse/daed@v0.1.1...v0.2.0

What happened

What you expect to happen

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know

Environment

• daed version (use daed --version):
• OS (e.g cat /etc/os-release):
• Kernel (e.g. uname -a):
• Others:

Context

🚀 @daebot proposed the following changelogs for release v0.1.0 generated in workflow run.

Changelogs

Full Changelog

• fix: default googledns add tcp #92 (kunish)
• chore(sync): keep upstream source up-to-date #90 (dae-bot[bot])
• chore(sync): keep upstream source up-to-date #86 (dae-bot[bot])
• refactor: split orchestrate page into multiple components #81 (kunish)
• feat: restrict drag and drop area #80 (kunish)
• feat: drag nodes and subscriptions between groups #79 (kunish)
• fix(subscription): loading indicator of update #78 (kunish)
• feat(group): show subscription tag on node hover #77 (kunish)
• ci: add sync-upstream workflow #76 (yqlbu)
• ci(prerelease): include v*.*.*rc* (v0.1.1rc1) case #75 (yqlbu)
• ci(release): retrieve release tag (version) from dispatch inputs #74 (yqlbu)
• fix(config): disable allow insecure by default #73 (kunish)
• feat(config): show interface ip addresses in interface select #72 (kunish)
• feat: add description text for group policies #71 (kunish)
• feat: add loading state indicators #70 (kunish)
• chore(issue-template): update default labels for bug-report #69 (yqlbu)
• ci(build-nightly): add fetch-depth: 0 #67 (kunish)

What happened

What you expect to happen

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know

Environment

• daed version (use daed --version):
• OS (e.g cat /etc/os-release):
• Kernel (e.g. uname -a):
• Others:

Summary

Reproducing release automation by @daebot. See screenshots in as comments below.

What feature you would like us to integrate into the daed project

Why is this needed

What happened

What you expect to happen

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know

Environment

• daed version (use daed --version):
• OS (e.g cat /etc/os-release):
• Kernel (e.g. uname -a):
• Others:

What happened

What you expect to happen

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know

Environment

• daed version (use daed --version):
• OS (e.g cat /etc/os-release):
• Kernel (e.g. uname -a):
• Others:

What happened

What you expect to happen

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know

Environment

• daed version (use daed --version):
• OS (e.g cat /etc/os-release):
• Kernel (e.g. uname -a):
• Others:

What happened

What you expect to happen

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know

Environment

• daed version (use daed --version):
• OS (e.g cat /etc/os-release):
• Kernel (e.g. uname -a):
• Others:

What feature you would like us to integrate into the daed project

Why is this needed

What happened

None

What you expect to happen

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know

Environment

• daed version (use daed --version):
• OS (e.g cat /etc/os-release):
• Kernel (e.g. uname -a):
• Others:

What happened

What you expect to happen

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know

Environment

• daed version (use daed --version):
• OS (e.g cat /etc/os-release):
• Kernel (e.g. uname -a):
• Others:

What happened

What you expect to happen

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know

Environment

• daed version (use daed --version):
• OS (e.g cat /etc/os-release):
• Kernel (e.g. uname -a):
• Others:

What happened

What you expect to happen

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know

Environment

• daed version (use daed --version):
• OS (e.g cat /etc/os-release):
• Kernel (e.g. uname -a):
• Others:

What would you like us to improve

Why is this needed