ALR-PUBLISH(1)

πŸ“¦
version 1.2.1 Β· 2 versions
, in debian trixie, ubuntu questing, ubuntu resolute, ubuntu stonking

✨ alr-publish β€” the Alire manual, bestie edition ✨

okay so this is the page for alr-publish(1), straight out of the Alire manual (the man page is literally titled ALR-PUBLISH(1), in case you were wondering). she helps you publish a new release πŸŽ€ and she is so much less scary than she looks. let's get into it πŸ’…


🌸 NAME 🌸

alr-publish β€” help with the publication of a new release


πŸ¦‹ SYNOPSIS πŸ¦‹

alr publish [options] [--skip-build] [--tar] [--manifest <file>] [<URL>
[commit]]]

that's the whole vibe. options, then optionally skip the build, optionally make a tar, optionally point at a different manifest, optionally hand her a <URL> and maybe a commit. mix and match, she's flexible πŸ’–


✨ OPTIONS ✨

  • --manifest=ARG β€” picks a manifest file that is not ./alire.toml. like, you have a different toml and you want her to use that one instead. go off, custom girl 🫢
  • --tar β€” wakes up the publishing assistant so she builds a source archive out of a local directory. the "i have files right here, package them up" route 🌈
  • --trusted-sites β€” just prints you a list of the trusted git repository sites. no publishing, no ceremony, just the list πŸ‘‘
  • --skip-build β€” skips the build check step. yes, the check. she's not going to build-verify for you, so know what you're doing πŸ™ˆ

πŸ’œ GLOBAL OPTIONS πŸ’œ

these ones are the everywhere-options, the ones that work across the whole alr universe, not just publishing:

  • -c, --config=ARG β€” overrides where the configuration folder lives. want your config somewhere else? say it here ✨
  • -f, --force β€” keeps going after a recoverable troublesome situation. like, "yeah i know, push through anyway" energy πŸ’€
  • -h, --help β€” shows general help, or help specific to whatever command you typed. the classic save-me button πŸ†˜
  • -n, --non-interactive β€” assumes the default answer for every single prompt. no questions asked, literally 🌸
  • --no-color β€” turns off colors in the output. for when your terminal aesthetic is monochrome πŸ–€
  • --no-tty β€” disables control characters in output. good for pipes and logs and places that do not want fancy business πŸŽ€
  • --prefer-oldest β€” when resolving dependencies, prefers the oldest versions instead of the newest. vintage queen πŸ“
  • --version β€” displays the version and dips out immediately πŸ‘‹
  • -q β€” limits output to errors only. quiet mode, mysterious mode πŸ¦‹
  • -v β€” be more verbose. use it twice for extra detail. yes bestie, stack them ⭐
  • -d, --debug[] β€” enables debug-specific log messages. for when you need to see everything πŸ”₯

🌈 DESCRIPTION 🌈

she checks a release and generates an index manifest. that's the core gig, no cap πŸ’…

the full details live at https://github.com/alire-project/alire/blob/master/doc/publishing.md

so about that <URL> β€” it's an optional path to a remote source archive, or a local or remote git repository. she takes all of those 🫢

for the common use case of a github-hosted repository: issue alr publish after committing and pushing the new release version. commit first, push first, then publish. order matters, iykyk ✨

  • use --tar to create a source archive that's ready to be uploaded πŸ“¦
  • use --manifest to use metadata that lives in a non-default file πŸ—‚οΈ

and for help with all the other scenarios, go check that link up above πŸ‘† she said what she said.


πŸ‘€ SEE ALSO πŸ‘€


πŸŽ€ AUTHOR πŸŽ€

Generated with generate-man from Alire execution. iconic behaviour, honestly.


heads up bestie: --skip-build literally skips the build check step, so please don't be shocked when the build check doesn't happen πŸ’€

okay that's the whole page!! this was Alire 1.2, dated Aug 3, 2022 β€” she's a little vintage but she ate, periodt πŸ’–βœ¨πŸ¦‹

πŸ“¦ where this page comes from