Commit Graph

18 Commits

Author SHA1 Message Date
Junegunn Choi
2023011763
0.36.0 2023-01-17 01:33:05 +09:00
Junegunn Choi
d01ae55109
0.35.0 2022-11-12 00:58:06 +09:00
Junegunn Choi
04d0b0223f
0.34.0 2022-09-28 23:22:31 +09:00
Junegunn Choi
e03ac3136e
0.33.0 2022-08-29 07:23:14 +09:00
Junegunn Choi
f7e7259910
0.32.0 2022-08-02 21:56:14 +09:00
Junegunn Choi
ecc418ba77
0.31.0 2022-07-21 23:04:57 +09:00
Junegunn Choi
2093667548
0.30.0 2022-04-04 23:01:43 +09:00
Junegunn Choi
dc975e8974
0.29.0 2021-12-25 01:46:01 +09:00
Junegunn Choi
e4c3ecc57e
0.28.0 2021-11-04 01:05:07 +09:00
Junegunn Choi
19759ed36e
0.27.0 2021-04-06 22:53:59 +09:00
Junegunn Choi
34fe5ab143
0.26.0 2021-03-13 15:13:31 +09:00
calvin ardi
bf447d7703
Update default number version (#2307) 2021-01-08 13:35:46 +09:00
Junegunn Choi
b5e0e29ec6
Assign default number version (without patch version)
So that you can still build and use fzf even when the precise version
number is not injected via -ldflags.
2020-10-29 01:38:34 +09:00
Junegunn Choi
3304f284a5
Panic when fzf was built without version information
So that the package maintainers would immediately know that the build is
incorrect. But is there a way to make build simply fail?

Related: https://github.com/junegunn/fzf.vim/issues/1150
2020-10-28 10:51:32 +09:00
Junegunn Choi
552414978e
0.24.0-rc1 2020-10-27 11:07:27 +09:00
Aaron Bieber
a1bcdc225e Add pledge(2) support (OpenBSD only) via a 'protector' package. (#1297) 2020-01-19 14:13:32 +09:00
Junegunn Choi
83e9af6601
Add git revision to --version output 2017-06-02 17:59:12 +09:00
Junegunn Choi
8bbf9335e1
Restructuring: main package in project root 2017-06-02 17:59:01 +09:00