Struggling with tagged release build

[Marvbudd]

I've read several articles on tagged releases and they are not explaining sufficient detail that I'm able to get the job done. It seems everyone has their own based on github actions. Like https://github.com/marketplace/actions/github-upload-release-artifacts and https://github.com/marvinpinto/action-automatic-releases. But are these necessary? I'm wary of just using someone else's code in case they change. I suppose I could fork (is that the right term? I'm new at github)
I also see some complex implementation in electron-builder that, if I can make it work, I would prefer an integrated solution. But what I've tried is not working and I've seen someone else bypass the uploading of artifacts with option ---publish,never, and then proceed to use a solution like the above. But why?
So back to what I'm seeing:
My package.json:
"scripts": {
"dist": "electron-builder",

Here is my job in builds.yaml clipped so it fits here:
jobs:
build_on_mac:
runs-on: macOS-latest
steps:
- uses: actions/checkout@master
with:
ref: main
- uses: actions/setup-node@master
with:
node-version: 17.3
- name: see directory
run: ls
- name: Install dependencies
run: yarn install
- name: Build on MacOS
run: yarn run dist
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
DEBUG: electron-builder

And the workflow output excerpt where I see the problem is:
• async task error error=404 Not Found
"method: GET url: https://api.github.com/repos/Marvbudd/shoebox-releases/releases\n\nPlease double check that your authentication token is correct. Due to security reasons, actual status maybe not reported, but 404.\n"
Headers: {

It looks to me like it is trying, and my GITHUB_TOKEN is incorrect. Everywhere it says this token is automatically provided. What am I doing wrong? Will the code I have above put it in the project's Release artifact tab as I'm hoping? What is a better plan?
"devDependencies": {
"electron": "^17.1.0",
"electron-builder": "^22.14.13"
}

[Marvbudd]

I finally got the URL set to something that does not error. But I do not see any artifacts uploaded. Still puzzled why I can't get this.

[webknjaz]

It looks like you're asking in the wrong place. This action's sole purpose is to publish Python distribution packages to PyPI.