Auto release new minor versions #33

zen0bit · 2024-02-28T18:16:16Z

No description provided.

zen0bit · 2024-02-28T18:17:55Z

Major version bump should be done manually

zen0bit · 2024-02-28T18:20:36Z

Preview

mckaygerhard · 2024-02-29T14:26:57Z

👍 great! hey, the trigger is? i mean when this "auto" release tag will be deploy? witch action does the triggering ?

mckaygerhard · 2024-02-29T14:28:02Z

i mean you put

on: 
  push:
    branches:
      - master

this has a problem, on any commit+push we will have a release no matter is there is a test failing or not!

so your proposal maybe is : have a stable branch for release and a develop branch ?

vaisarger · 2024-02-29T14:45:38Z

I agree with @mckaygerhard ...

"Automated" release naming would be done even in case there is a test failing, or anything else failing, that is, e.g., I don't want a new release (at least, I don't want it yet ).

zen0bit · 2024-02-29T18:31:15Z

👍 great! hey, the trigger is? i mean when this "auto" release tag will be deploy? witch action does the triggering ?

trigger could be whatever you want, could run only after success test.. (change needed)

Or bind to tag (major minor patch no-release)

automated releases could be named like you want (marked as you want pre-release, latest etc)

so your proposal maybe is : have a stable branch for release and a develop branch ?

That is good practice

vaisarger · 2024-02-29T18:44:19Z

So, if I've got it properly, when I type in my terminal:
git push github master

then Github would create, say, the version 12.0.7 of EBG, automatically?

Am I correct ?

zen0bit · 2024-02-29T18:46:55Z

12.1.0

in this PR could be changed
12 major
.1 minor

don't know what patch do differently

zen0bit · 2024-02-29T18:50:55Z

Or you can use bash in github action for anything you want..
(on my learning list)

vaisarger · 2024-02-29T18:53:30Z

So, my friend... We would have only 9 possible changes before major version change...

This project is not so "live & working", anyway I see this as a limitation...

@mckaygerhard what do you think about?

zen0bit · 2024-02-29T18:54:28Z

12.99.0

zen0bit · 2024-02-29T18:56:39Z

its scripting, anything isn't set in stones (i hope)
anything is possible, you just need figured out how could be changed...

only boundary is your imagination
right?

vaisarger · 2024-02-29T19:01:08Z

12.99.0

Oh ! right ! :P

Or you can use bash in github action for anything you want..

Namely, you are saying that, e.g. for a potential 12.0.7, I still could do pushing by a new tag from my terminal ?

anything is possible, you just need figured out how could be changed...

I absolutely agree ! you know... I'm just trying to realize because I'm not at all Github expert: only for this reason!

zen0bit · 2024-02-29T19:01:29Z

So, my friend... We would have only 9 possible changes before major version change...

you are not! we are working with computers which can oprate with anything we will give them. (not only 1-9)

This project is not so "live & working", anyway I see this as a limitation...

@mckaygerhard what do you think about?

vaisarger · 2024-02-29T19:06:03Z

I'm seriously considering it...

With this auto-versioning... Is still possible changing version manually by tag, from terminal?

zen0bit · 2024-02-29T19:07:55Z

12.99.0

Oh ! right ! :P

Or you can use bash in github action for anything you want..

Namely, you are saying that, e.g. for a potential 12.0.7, I still could do pushing by a new tag from my terminal ?

sure
(not yet get used to githubcli except pushing/pulling everything done on github webui.)

or can be triggered only manually. so one click for you with version change (which one you choose) with complet changelog in few seconds

or better don't ask what you can, tell what you want...

anything is possible, you just need figured out how could be changed...

anything is possible, you just need figured out how could be changed...

I absolutely agree ! you know... I'm just trying to realize because I'm not at all Github expert: only for this reason!

Me to, just bit more experienced, since working against actions often 😃

vaisarger · 2024-02-29T19:13:14Z

I hope my question will not mind you... (really):

If I possibly would change my mind about auto-versioning, how could I come back?

zen0bit · 2024-02-29T19:15:53Z

that minor major patch no0release could be also override with appropriate label in PR name

look on actions READMEs in repo itself...
action-automatic-release
release-action
action-gh-release

If I possibly would change my mind about auto-versioning, how could I come back?

just delete yml file or change trigger in action to worflow_dispatch only (manual trigger)

zen0bit · 2024-02-29T19:17:11Z

don't ask what you can, tell what you want...

vaisarger · 2024-02-29T19:19:36Z

just delete yml file

And where will be that file? In same location of LICENSE file ?

zen0bit · 2024-02-29T19:25:00Z

look at 1 changed file in this PR

under .github/workflows/any-name-you-want.yml

PS: added some comments inside file to better understand..

vaisarger · 2024-02-29T19:28:33Z

look at 1 changed file in this PR PS: added some comments inside file to better understand..

Thank you very much, now is more understandable! :P

Still I didn't understand where will go that .yml file in EBG tarball...

zen0bit · 2024-02-29T19:34:38Z

nowhere. its hidden file just for github.

it's why is under .github/

(like github dotfile)

mckaygerhard · 2024-02-29T19:38:21Z

I'm seriously considering it...

With this auto-versioning... Is still possible changing version manually by tag, from terminal?

@zen0bit change the script to use tags.. that solve the problem for @vaisarger so he can decide when release using tag marks

vaisarger · 2024-02-29T19:40:26Z

nowhere. its hidden file just for github.

it's why is under .github/

I don't have that directory... where is ? (sorry )

mckaygerhard · 2024-02-29T19:42:37Z

nowhere. its hidden file just for github.

it's why is under .github/

I don't have that directory... where is ? (sorry )

ls -la will show you.. any dir with dot as prefix will be hidden in linux

also if you dont have the changes from him will not have such change and directory! dont worry

such directory .github/* is only for github actions.. nothing more..

by the way i posted a message before for him! maybe will help to you

zen0bit · 2024-02-29T19:47:01Z

Or you can create release[anyname] branch and if you push changes there, that will trigger new release..

zen0bit · 2024-02-29T21:19:14Z

nowhere. its hidden file just for github.

it's why is under .github/

I don't have that directory... where is ? (sorry )

sure, create only if needed

zen0bit · 2024-02-29T21:22:57Z

I added a lot comments etc. to better see how github workflow works..
Now is more a like template and also "Hello world" to see easy use of bash...

mckaygerhard · 2024-02-29T22:02:23Z

.github/workflows/auto-release.yml

+    #paths-ignore: [ '**/README.md' ]
+
+    # Triggers the workflow if matching tag is created
+    tags: [ 'v*.*' ]


now we must explain to @vaisarger that will only trigerr when make a custom tag..

@vaisarger it means no release will be publised .. and only if you tagged will be publised

zen0bit · 2024-02-29T22:30:16Z

Just define what exactly wanna achieve and your current workflow/staff used

mckaygerhard · 2024-03-01T12:11:11Z

Just define what exactly wanna achieve and your current workflow/staff used

yes looks good to me!

vaisarger · 2024-03-11T12:14:43Z

Sorry guys, we Open Source developers have a (tough) life also... :P
I would ask you to confirm two things about this PR:

If merged, a .github dir will appear in my local project directory?
with last change, only if I set a new tag (typing in terminal e.g.: git tag -a 13.0 -m "Brand new EBG version" ), github will trigger a new version... But, typing only: git push github master then no new version will be created?

Thank you for your patience...

zen0bit · 2024-03-12T10:45:11Z

If merged, a .github dir will appear in my local project directory?

yes

with last change, only if I set a new tag (typing in terminal e.g.: git tag -a 13.0 -m "Brand new EBG version" ), github will trigger a new version...

On line 21 tag is set to
tags: [ 'v*.*' ] So only if match this pattern...

You can look at my repo where I am trying that. (WebUI) In actions and releases you see..

Used this command to add and push git tag -a v0.8.0 -m "Brand new EBG version test" && git push gh v0.8.0 (I named my REMOTE gh since on github)

tag must match next elease number, because action will create number depending on last number not that you provided..

But, typing only: git push github master then no new version will be created?

yes

Here is full yaml file from author:

# action.yml
name: 'Tag/Release on Push Action'
description: 'Creates a Tag/Release on Push. Generates Release Notes. Customizable with Pull Request Labels'
author: 'rymndhng'
inputs:
  bump_version_scheme:
    description: 'The bumping scheme to use by default. One of minor|major|patch|norelease'
    required: true
  release_body:
    description: "Additional text to insert into the release's body."
    required: false
  tag_prefix:
    description: "Prefix to append to git tags. To unset this, set version_prefix to an empty string."
    required: false
    default: 'v'
  release_name:
    description: |
      Name of the release. Supports these template variables:

        <RELEASE_VERSION> the version number, e.g. "1.2.3"
        <RELEASE_TAG>     the git tag name, e.g. "v1.2.3"
    required: true
    default: '<RELEASE_TAG>'
  max_commits:
    description: "Maximum number of commits to add to release body"
    required: false
    default: 50
  use_github_release_notes:
    description: "When set to 'true', uses Github's Generated Release Notes instead of this plugin's release notes"
    required: false
    default: "false"
  dry_run:
    description: "When set to 'true', will compute the next tag, but will not create a release."
    required: false
    default: "false"
outputs:
  tag_name:
    description: 'Tag of released version'
  version:
    description: 'Version of release'
  body:
    description: 'Github Release Body in Text'
  upload_url:
    description: 'Github Release Upload URL'
runs:
  using: 'docker'
  image: 'Dockerfile'
branding:
  icon: 'award'
  color: 'blue'

And repo for README etc...

vaisarger · 2024-03-12T21:41:33Z

Ok. Now...

I usually use these commands to add and push:
git tag -a "13.0.0" -m "Brand new EBG version" && git push --tags github master

...

After this PR, what will the list of commands look like?
Maybe this:
git tag -a "v.13.0.0" -m "Brand new EBG version" && git push master v.13.0.0

???

mckaygerhard · 2024-03-13T12:47:57Z

I usually use these commands to add and push: git tag -a "13.0.0" -m "Brand new EBG version" && git push --tags github master
...
After this PR, what will the list of commands look like? Maybe this: git tag -a "v.13.0.0" -m "Brand new EBG version" && git push master v.13.0.0

umm now makes sense to me your questions. . @zen0bit needs a letter like "v" to discern if the tag is to make a release, but you do not use letters and use only numbers.. umm i have some ideas to improve your PR @zen0bit but i will check it in deep only this weekend..

mckaygerhard · 2024-03-13T12:53:30Z

@vaisarger i tested and if you want to be release only on tags we can change the behaviour but liked the idea!

zen0bit · 2024-03-13T13:24:25Z

look at second PR and again at my repo to what happened...

zen0bit · 2024-03-13T15:04:27Z

we can close this I think...

mckaygerhard · 2024-03-13T19:07:53Z

seems you works so much @zen0bit yeah. close this and let @vaisarger check #36 that it follows the schema number as X.Y.Z for tags releases

zen0bit · 2024-03-13T20:22:48Z

Completed in #36

Create auto-release.yml #3

9989412

Update auto-release.yml

6e82825

Update auto-release.yml

392e505

Update auto-release.yml

bde1232

mckaygerhard reviewed Feb 29, 2024

View reviewed changes

zen0bit closed this Mar 13, 2024

zen0bit reopened this Mar 13, 2024

zen0bit added 2 commits March 13, 2024 14:03

Update auto-release.yml

a534089

Update auto-release.yml

52e986f

Update auto-release.yml

006fad6

zen0bit force-pushed the master branch from 3ee6384 to 006fad6 Compare March 13, 2024 13:28

zen0bit closed this Mar 13, 2024

Auto release new minor versions #33

Auto release new minor versions #33

Conversation

zen0bit commented Feb 28, 2024

zen0bit commented Feb 28, 2024

zen0bit commented Feb 28, 2024

mckaygerhard commented Feb 29, 2024

mckaygerhard commented Feb 29, 2024 • edited Loading

vaisarger commented Feb 29, 2024

zen0bit commented Feb 29, 2024

vaisarger commented Feb 29, 2024

zen0bit commented Feb 29, 2024 • edited Loading

zen0bit commented Feb 29, 2024 • edited Loading

vaisarger commented Feb 29, 2024

zen0bit commented Feb 29, 2024

zen0bit commented Feb 29, 2024 • edited Loading

vaisarger commented Feb 29, 2024 • edited Loading

zen0bit commented Feb 29, 2024

vaisarger commented Feb 29, 2024

zen0bit commented Feb 29, 2024 • edited Loading

vaisarger commented Feb 29, 2024

zen0bit commented Feb 29, 2024 • edited Loading

zen0bit commented Feb 29, 2024

vaisarger commented Feb 29, 2024

zen0bit commented Feb 29, 2024 • edited Loading

vaisarger commented Feb 29, 2024

zen0bit commented Feb 29, 2024 • edited Loading

mckaygerhard commented Feb 29, 2024

vaisarger commented Feb 29, 2024 • edited Loading

mckaygerhard commented Feb 29, 2024

zen0bit commented Feb 29, 2024

zen0bit commented Feb 29, 2024

zen0bit commented Feb 29, 2024

mckaygerhard Feb 29, 2024

Choose a reason for hiding this comment

zen0bit commented Feb 29, 2024

mckaygerhard commented Mar 1, 2024

vaisarger commented Mar 11, 2024

zen0bit commented Mar 12, 2024 • edited Loading

vaisarger commented Mar 12, 2024

mckaygerhard commented Mar 13, 2024

mckaygerhard commented Mar 13, 2024

zen0bit commented Mar 13, 2024 • edited Loading

zen0bit commented Mar 13, 2024 • edited Loading

mckaygerhard commented Mar 13, 2024

zen0bit commented Mar 13, 2024 • edited Loading

mckaygerhard commented Feb 29, 2024 •

edited

Loading

zen0bit commented Feb 29, 2024 •

edited

Loading

zen0bit commented Feb 29, 2024 •

edited

Loading

zen0bit commented Feb 29, 2024 •

edited

Loading

vaisarger commented Feb 29, 2024 •

edited

Loading

zen0bit commented Feb 29, 2024 •

edited

Loading

zen0bit commented Feb 29, 2024 •

edited

Loading

zen0bit commented Feb 29, 2024 •

edited

Loading

zen0bit commented Feb 29, 2024 •

edited

Loading

vaisarger commented Feb 29, 2024 •

edited

Loading

zen0bit commented Mar 12, 2024 •

edited

Loading

zen0bit commented Mar 13, 2024 •

edited

Loading

zen0bit commented Mar 13, 2024 •

edited

Loading

zen0bit commented Mar 13, 2024 •

edited

Loading