v0.2.2

Changelog

New Features

• 9382147: !feat(ssl): add ssl over tls support for connecting to remote mysql database when certain providers does not insecure http connections & remove uncessary emojis from interactive reponse messages avoiding uncompatible encodings across systems (@andatoshiki)

Bug fixes

• bf54c92: fix(ci): fix config yml grammatical syntax for action workflow on prohibited concurrent trigger event fields (@andatoshiki)

Others

• 8c27e1e: chore(i18n): replace translation strings for more accurate language usgaes (@andatoshiki)
• 6cd9e5a: chore(i18n): update en-us translation locales with improved grammar strauctures of interactive bot responsives & emoji(s) at start of each message for visual interactions & update event triggers for actions on push of different branches and pull requests (@andatoshiki)
• 58b1d27: ci(docker): update docker action trigger event with test run while commit push & update authentication token for ghcr publishing authorization (@andatoshiki)
• 48204be: ci(trigger): add initiation trigger when pushing commits on to all brnches as well to all tags (@andatoshiki)

💖 Beta stage of v0.2.1-en-us is now Hot Released with English i18n Supported

1: Release Details

1.1: Major Changes

V0.2.1-en-us is finally hot out of the oven after approximately 5 months of my inaction on development activities; the update is maily included within the name of the release tag, I decided to adopt English i18n locales as a global bot language option instead of using vague anime style-oriented Chinese interactive language which disregards the professionalism of the entire projects; since the estimated size of the text string compared with Chinese characters are relatively more in word counts and higher in bundled sizing for compiled executables, thus relatively 1~2 mb in final binary size will likely to be greater as opposed to the prior versions. As to be noted that versions below v0.2.1 with Chinese i18n support will not be inactive on development yet supports of the piroir version will be discontinued after the English locales are fully appllied and adpoted once finished, lower verions will be remained in legacies. I recommend user fully migrate the bot to the latest version.

1.2: Minor Changes

Other minor changes aside from locales translations are build configs of the overall bot to align with the guidliness by goreleaser, while the built artifacts naming replacement field was deprecated since 2022-11-24 which was when I was on hiatus on my develpment activity for flight preparation for moving to teh United States for academic studies (by the way I'm at Temep in Arizona ;) welcomed invite me out for a meal); thus you might notice in the action tab where recent workflows completely fails and throws unmarshalled errors throughout releasing processes due to false yaml config syntaxes; yet another inept and careless action I took which resulted in failing workflows is by creating a separate branch while expecting GitHub could trigger release action from a specific commit or branch by setting the following configs for running workflows from en-us branch with the latest commits and changes updated while the precedence of release when tag created is still on the main master branch of the repository,

# ...
on:
  push:
    branches:
      - en-us
      - master
    tags:
      - '*'

Meanwhile the master branch still remains the workflow configs of prior versions since no pull request actions are being requested for branch merging. Hereby I was preplexed for the causes for failing workflows; but as soon as the two branches are merged, the issue seemed to be resolved. While the other options seems to be specifying specific release tags in order to trigger an action process for building; but writing commit messages to the convention was way out of my patience (plainly lazy).

Referring to the official deprecation notice of config fields from the goreleaser documentation manual mentioned above,

The replacements will be removed soon from the archives section, as it was never handled correctly when multiple archives were being used, and it also causes confusion in other places.

You can still get the same features by abusing the name_template property.

The replacement field for altering the final naming of the packed acrhive to personalized indicators, the traditional configs using default yaml syntaxes fails and instantly terminate the building processes. The migration of goreleaser requires naming tempaltes in go grammars that more explicitly indicates how the original naming conventions could be adpated, in follows,

archives:
  # - name_template: '{{ .ProjectName }}_{{ .Os }}_{{ .Arch }}{{ if .Arm }}v{{ .Arm }}{{ end }}'
  #   replacements:
  #     darwin: Darwin
  #     linux: Linux
  #     windows: Windows
  #     386: 32bit
  #     amd64: 64bit
  - name_template: >-
      {{- .ProjectName }}_
      {{- title .Os }}_
      {{- if eq .Arch "amd64" }}64bit
      {{- else if eq .Arch "386" }}32bit
      {{- else }}{{ .Arch }}{{ end }}
      {{- if .Arm }}v{{ .Arm }}{{ end -}}
    format_overrides:
      - goos: windows
        format: zip
    files:
      # - README.md
      - config.yml.example
      - LICENSE

The deprecated replacement configs are comment out above with the new naming templates followed for a direct comparison.
New buid pahses of action workflows are added as a intermediary step for performing extra checks for security improvements with logical build process to reduce abundant compilation time.

Warning
Note that this is only a pre-release in a test version for validating successful build actions, but the executables should be completely functional use on production stage, I recommend you to wait for the final complete version with all minor changes and details tweaked before you download and run the latest releases.
As well, the docker workflow hasn't been fixed yet; the publishing process stucks at logging into ghcr.io registry for releasing packaging; hereby an apology to docker users, you will still have to bare with the prior Chinese versions until I stops to procrastinate for an update on the docker images; but I DO NOT GUARANTEE the time of committing changes to the repo again in the future from now. ;p I am absolutely lazy.

The more detailed commits are listed as followed in chronological order by commits with messages, (I personally write detailed commit messages despite conventional commits requires less lengthy details after scoop as a personal habit)

2: Changelog

2.1: Bug fixes

• 61e31b5: fix(action): rewrite goreleaser configuration for avoiding overlapped or repeated archives after builds for corresponded to each arch or goos that causes naming duplication (@Anda Toshiki)
• 97d97b1: fix(action): rmeove replacement key field for built artifacts archive naming after packing for preventing build from failing due to deprecation migration of goreleaser from v2 to v3 (@Anda Toshiki)
• fa5e2b4: fix(build): rollback the goreleaser action to v2 for successful builds compatible with elder build configs (@Anda Toshiki)
• 823564a: fix(builds): fix goreleaser build configuration by replacing depcrecated field of archives.replacements with latest goreleaser archive templates in go grammar (@Anda Toshiki)
• 1a2f597: fix(workflow): add snapshot flag for building local execuctable outputs without failing while cleanup test build dirctory outputs (@Anda Toshiki)
• d8b8c39: fix(workflow): update workflow config with v3 version of goreleaser with new build phases while removing deprecated flags during build initiation process & add new workflow manual trigger of action or commit push to every branch with changes (@Anda Toshiki)
• 0cefd51: fix(workflows): reconfigure workflows for building release binary artifacts on en-us branch instead of master (@Anda Toshiki)

Others

• 624b6aa: feat(en-us): rewrite internal bot-user interaction message i18n to en-us locales targeting international users (@)
• 41fdffe: fix(global locales): completely retranslated bot interacting message to en-us locales & restructure both goreleaser and workflow configs for adapting version migration from deprecated legacy parameters of goreleaser (@Anda Toshiki)
• a4e43c4: perf(action): bump goreleaser action for binary compilation process to v3 instead of legacy with more stability and security improvements & avoiding new naming conventions of archive.Replacement property of dist will be fail during process (@Anda Toshiki)
• dd21078: upgrade(workflow): bump legacy version of goreleaser action for building process to incooperate with naming convnetion templates after deprecation of v2 in archive naming replacement field in config property (@Anda Toshiki)

v0.2.1

Under tons of factor (mainly procrastination) on a lot of other fun and small projects, I finally decided to release this version specifically for Docker favored users and such. Instead of the traditional Docker registry, I personally preferred to stick with the GitHub ecosystem on nearly everything related to development for environment unification.

This release's source includes an action pulled from ghcr.io's tutorial for building docker image and publish to ghcr.io GitHub registry, users will be able to directly run docker pull from GitHub in one-liner command for running the bot with some simple configuration. But I DO NOT guarantee bloated bugs of any type, since this is only the trial build, use at your own risk, welcome to feedback any issues in issues tab. Below are the commit logs in case you would like to target specific commit and point out issues for changes.

• eb46734 fix(docker): make docker build action trigger on release
• 0f2fd8c fix(docker): make docker build action unignore tags
• eea6aae fix(docker): made trigger in wrong action now in docker
• 767a6e9 fix(docker): fix docker biuld action trigger on push via specifying branch
• 486838d feat!(docker): add docker build action for ghrc registry
• 3811857 fix(docker): rename package in dockerfile for image rebuild

Other then these, happy bot hosting dev folks! Happy Chinese New Year! :)

v0.2.0

• 7377b83 : doc(tutorial): replace short link of doc site to standalone site.
• 438fa2e : fix(config): remove some prior test infos from example config and replace with variable.
• 20f4851 : refactor: remove unnecessary infos on bots load in terminal.
  • The new documentations could be found at e5.toshiki.dev, link shorteners may cause service side to breach the revocation on permanently adding the long prior telegra.ph link, for in app reading if on phone, but with the new documentation side, users are required to click out of the telegram app to read, but with a better experience on load, especially for those mainland China users whom does not have a strong support of the proxy to load telegra.ph.

The repo of the documentation site is at andatoshiki/toshiki-e5subot-doc, well come to contribute to UI changes, or grammar fixings of any type, PR welcomed!

v0.1.2

• Fixed messy links
• Fixed missing ( in bot messages

v0.1.1

• Added moe language i18n translation for bot interface
• (I hate writing docs and changelogs/release notes)

Full Changelog: v0.0.1...v0.1.1

v0.0.1

Full Changelog: https://github.com/andatoshiki/toshiki-e5subot/commits/v0.0.1