# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 33
# self = https://watcher.sour.is/conv/woeyf2q
@prologic you think its time the version to get bumped? :)
@xuu Yes but I was hoping to get this issue before releasing a v1.0 so we have proper prebuilt binaries against for various platforms. You any good at this type of thing? cross-platform builds/etc?
@xuu Yes but I was hoping to get this issue before releasing a v1.0 so we have proper prebuilt binaries against for various platforms. You any good at this type of thing? cross-platform builds/etc?
@xuu Yes but I was hoping to get this issue before releasing a v1.0 so we have proper prebuilt binaries against for various platforms. You any good at this type of thing? cross-platform builds/etc?
more or less. :D
what are you using to ci/cd? i dont see a travisci/circleci/etc in the repo.. i can put something together to bump the patch level on master branch merges.
more or less. :D
what are you using to ci/cd? i dont see a travisci/circleci/etc in the repo.. i can put something together to bump the patch level on master branch merges.
more or less. :D\nwhat are you using to ci/cd? i dont see a travisci/circleci/etc in the repo.. i can put something together to bump the patch level on master branch merges.
more or less. :D
what are you using to ci/cd? i dont see a travisci/circleci/etc in the repo.. i can put something together to bump the patch level on master branch merges.
more or less. :D\nwhat are you using to ci/cd? i dont see a travisci/circleci/etc in the repo.. i can put something together to bump the patch level on master branch merges.
So all my projects use Github Actions. You can see in .github/workflows/ The main issue with releasing a new version at the moment is building new binaries with goreleaser.
So all my projects use Github Actions. You can see in .github/workflows/ The main issue with releasing a new version at the moment is building new binaries with goreleaser.
So all my projects use Github Actions. You can see in .github/workflows/ The main issue with releasing a new version at the moment is building new binaries with goreleaser.
If you have a read of the linked items in that issue you'll see what the problem is. Basically I have been doing the releases on my mac, and cross-compilation fails for various targets now due to various CGo dependencies used in the project. I'd like to continue using goreleaser if we can, but we might have to do the actual release builds in CI instead in a Github Action runner. But you _may_ still have to use the cross-cross complie magic referenced in that issue anyway to go from Linux -> other
If you have a read of the linked items in that issue you'll see what the problem is. Basically I have been doing the releases on my mac, and cross-compilation fails for various targets now due to various CGo dependencies used in the project. I'd like to continue using goreleaser if we can, but we might have to do the actual release builds in CI instead in a Github Action runner. But you _may_ still have to use the cross-cross complie magic referenced in that issue anyway to go from Linux -> other
If you have a read of the linked items in that issue you'll see what the problem is. Basically I have been doing the releases on my mac, and cross-compilation fails for various targets now due to various CGo dependencies used in the project. I'd like to continue using goreleaser if we can, but we might have to do the actual release builds in CI instead in a Github Action runner. But you _may_ still have to use the cross-cross complie magic referenced in that issue anyway to go from Linux -> other
@prologic have you tried using the macos github build environment? looks like they have a windows one too.
@prologic have you tried using the macos github build environment? looks like they have a windows one too.
@prologic have you tried using the macos github build environment? looks like they have a windows one too.
@prologic have you tried using the macos github build environment? looks like they have a windows one too.
@xuu @prologic oh.. you are.. maybe i don't understand the issue with building?
@xuu @prologic oh.. you are.. maybe i don't understand the issue with building?
@xuu @prologic oh.. you are.. maybe i don't understand the issue with building?
@xuu @prologic oh.. you are.. maybe i don't understand the issue with building?
@xuu The issue is that goreleaser is probably no longer a viable tool here to build binaries to attach to the release. It cross-compiles and that doesn't work now that we depend on some CGo libraires. So maybe the solution is to move the release process entirely into Github Actions and use different tools to build and upload the binaries to the release? (_I've just always done releases up until now with goreleaser..._)
@xuu The issue is that goreleaser is probably no longer a viable tool here to build binaries to attach to the release. It cross-compiles and that doesn't work now that we depend on some CGo libraires. So maybe the solution is to move the release process entirely into Github Actions and use different tools to build and upload the binaries to the release? (_I've just always done releases up until now with goreleaser..._)
@xuu The issue is that goreleaser is probably no longer a viable tool here to build binaries to attach to the release. It cross-compiles and that doesn't work now that we depend on some CGo libraires. So maybe the solution is to move the release process entirely into Github Actions and use different tools to build and upload the binaries to the release? (_I've just always done releases up until now with goreleaser..._)
@xuu Ahhh! Yes this was one of the possible ways I explored as well. This is awesome! if this all works and you can cut a release from this, put the PR up and let's release a v1.0 😀 Great work! 🙇♂️
@xuu Ahhh! Yes this was one of the possible ways I explored as well. This is awesome! if this all works and you can cut a release from this, put the PR up and let's release a v1.0 😀 Great work! 🙇♂️
@xuu Ahhh! Yes this was one of the possible ways I explored as well. This is awesome! if this all works and you can cut a release from this, put the PR up and let's release a v1.0 😀 Great work! 🙇♂️